ethereum.balances Table: ez_balances_native_daily Type: Base Table
What
This table provides daily native asset balance snapshots (ETH) by making directeth_getBalance RPC
calls at the end of each day. It captures the current native asset balance for each address that has
had native asset activity, providing a comprehensive view of native holdings with decimal
adjustments and USD valuations where available. Historical native balances data available, starting
from 2025-06-10.
Key Use Cases
- Daily portfolio tracking and native asset balance monitoring
- Historical native asset balance analysis and trend identification
- Whale tracking and large holder distribution analysis
- Daily balance snapshots for reporting and analytics
- Native asset concentration analysis across addresses
- Daily balance-based yield and return calculations for native assets
- End-of-day balance reconciliation and accounting
Important Relationships
- Join with fact_blocks: Use
block_numberfor block metadata and timestamps - Join with dim_labels: Use
addressfor entity identification and categorization - Join with ez_prices_hourly: USD valuations already included but can be refreshed
- Join with ez_balances_erc20_daily: Compare with ERC20 token daily balances
- Join with ez_native_transfers: Compare daily balances with transfer activity
- Join with core__fact_traces: Analyze native asset movement patterns
Commonly-used Fields
address: The account address holding the native asset balancebalance: Native asset balance at end of day, decimal adjusted to standard unitsbalance_usd: USD value of the native asset balance at end of daybalance_raw: Raw balance in smallest unit (Wei) without decimal adjustmentbalance_precise: Precise decimal-adjusted balance as stringbalance_hex: Hexadecimal balance as returned by eth_getBalancedecimals: Number of decimal places (always 18 for native assets)block_date: The date for which this balance snapshot was taken
Sample queries
Daily Native Asset Holdings by AddressColumns
| Column Name | Data Type | Description |
|---|---|---|
| BLOCK_NUMBER | NUMBER | Sequential counter representing the position of a block in the blockchain since genesis (block 0). |
| BLOCK_DATE | DATE | The date for which this balance snapshot represents the end-of-day native asset balance. |
| ADDRESS | TEXT | The account address whose native asset balance is recorded in this daily snapshot. |
| DECIMALS | NUMBER | Number of decimal places for the native asset (always 18 for ETH). |
| BALANCE_HEX | TEXT | Hexadecimal representation of the native asset balance as returned by the eth_getBalance RPC call. |
| BALANCE_RAW | NUMBER | Native asset balance in the smallest unit (Wei) without decimal adjustment, as returned by eth_getBalance. |
| BALANCE_PRECISE | TEXT | Native asset balance with proper decimal adjustment, returned as a string to preserve precision. |
| BALANCE | FLOAT | Native asset balance with decimal adjustment converted to a float for easier mathematical operations. |
| BALANCE_USD | FLOAT | USD value of the native asset balance at the end of the day, calculated using hourly price data. |
| EZ_BALANCES_NATIVE_DAILY_ID | TEXT | Primary key - unique identifier for each row ensuring data integrity. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the record was first added to the Flipside database. |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp of the most recent update to this record. |
- Immutable once finalized
- Primary ordering mechanism for blockchain data
- Increments by 1 for each new block
- Used as a proxy for time in many analyses
block_date and
address to ensure uniqueness of each daily balance snapshot.
Usage:
- Deduplication in incremental loads
- Join operations for data quality checks
- Troubleshooting specific records
- Identifying unique address-date combinations
- Data freshness monitoring - check when balance snapshots were loaded
- Incremental processing markers - identify latest loaded data
- Debugging data pipeline issues
- SLA tracking for daily balance updates
- Data corrections - fixing incorrect balance calculations
- Enrichment additions - adding missing metadata
- Reprocessing for accuracy - recalculation of balances or USD values
- Schema migrations - structural changes to the table