Skip to main content
Deprecation NoticeThis table will be removed from the platform on December 11, 2025 (4 weeks from November 13, 2025).Please migrate to the new standardized balances tables:
  • ethereum.balances.ez_balances_native_daily - Daily native ETH balance snapshots
  • ethereum.balances.ez_balances_erc20_daily - Daily ERC20 token balance snapshots
The new tables offer improved performance, daily granularity, USD pricing, and are standardized across all EVMs.
Schema: ethereum.core Table: ez_current_balances Type: View This table contains the current, non-zero balances for wallets on this EVM blockchain. Symbol, name, and price are joined where possible. Prices are calculated as of the last activity date and as of the most recently recorded hourly price. ERC721s are included. Please note - the underlying data for this is large. If you want your query to run quickly, please use filters as much as possible. Using at least last_activity_block_timestamp::date as a filter will lead to optimal query performance.

​
Columns

Column NameData TypeDescription
LAST_ACTIVITY_BLOCKNUMBERThe last block where this token was transferred by this address.
LAST_ACTIVITY_BLOCK_TIMESTAMPTIMESTAMP_NTZ
USER_ADDRESSTEXTThe wallet address holding the tokens / ETH.
CONTRACT_ADDRESSTEXTThe contract address of the token (null for ETH).
CURRENT_BAL_UNADJNUMBERThe current token or ETH balance for this address, without a decimal adjustment.
CURRENT_BALFLOATThe decimal adjusted current token or ETH balance.
USD_VALUE_LAST_ACTIVITYFLOATThe value of the tokens or ETH in USD, at the time the last token activity occurred. Will be null for tokens without a decimal.
USD_VALUE_NOWFLOATThe value of the tokens or ETH in USD, as of the most recently recorded hourly price. Will be null for tokens without a decimal.
SYMBOLTEXTThe symbol of the token contract, or ETH.
TOKEN_NAMETEXTThe name of the token contract, or Native ETH.
DECIMALSNUMBERThe decimals for the token contract.
HAS_DECIMALBOOLEANWhether the token has a decimal or not, either TRUE or FALSE.
HAS_PRICEBOOLEANWhether the token has an hourly price or not, either TRUE or FALSE.
LAST_RECORDED_PRICETIMESTAMP_NTZThe timestamp of the last hourly price recorded for this token.
EZ_CURRENT_BALANCES_IDTEXTPrimary key - unique identifier for each row ensuring data integrity.
Format: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns. Example: MD5(block_number, tx_hash, trace_index) Usage:
  • Deduplication in incremental loads
  • Join operations for data quality checks
  • Troubleshooting specific records
Important: Implementation varies by table - check table-specific documentation. | | INSERTED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the record was first added to the Flipside database. Format: TIMESTAMP_NTZ Use Cases:
  • Data freshness monitoring
  • Incremental processing markers
  • Debugging data pipeline issues
  • SLA tracking
Query Example: 
-- Check data latency
SELECT
    DATE_TRUNC('hour', block_timestamp) as block_hour,
    DATE_TRUNC('hour', inserted_timestamp) as insert_hour,
    AVG(TIMESTAMPDIFF('minute', block_timestamp, inserted_timestamp)) as avg_latency_minutes
FROM <blockchain_name>.core.fact_transactions
WHERE block_timestamp >= CURRENT_DATE - 1
GROUP BY 1, 2;
``` |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp of the most recent update to this record.

**Format**: TIMESTAMP_NTZ

**Triggers for Updates**:
- Data corrections
- Enrichment additions
- Reprocessing for accuracy
- Schema migrations

**Monitoring Usage**:
```sql
-- Recently modified records
SELECT *
FROM <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
AND modified_timestamp >= CURRENT_DATE - 1;

-- Data quality tracking
SELECT
    DATE(modified_timestamp) as mod_date,
    COUNT(*) as records_updated,
    COUNT(DISTINCT block_number) as blocks_affected
FROM <blockchain_name>.core.fact_transactions
WHERE modified_timestamp > inserted_timestamp
GROUP BY 1
ORDER BY 1 DESC;
``` |