Skip to main content
The ethereum dataset holds the standardized Ethereum tables. The four core tables follow the shared EVM layout; Ethereum additionally carries beacon_validators and uncle_blocks, which no other chain in the family publishes. Every column is documented at EVM β–Έ Overview.

Tables

TableDescription
blocksOne row per block, with its gas and fee totals.
transactionsOne row per transaction, with its receipt fields on the same row.
logsOne row per event log a contract emitted.
tracesOne row per internal call recorded during execution.
beacon_validatorsBeacon chain validator balances and statuses, snapshotted per slot.
uncle_blocksHeaders of the uncle blocks that canonical blocks reference.
blocks also carries a 1970-01-01 partition holding rows whose source timestamp is zero; the chain’s history starts 2015-07. uncle_blocks is a closed record: it ends at its 2022-09-15 partition, the day Ethereum stopped producing uncles.

Sample queries

The partition column differs by table: transactions, logs and traces split on block_timestamp, blocks splits on timestamp. Bound the right column in every query and keep it bare on the left of the comparison; wrapping it in a function reads every partition.
Count daily transactions and the accounts that sent them.

Notes

beacon_validators covers the consensus side of the chain. Ethereum runs two chains in step: the execution chain that holds transactions, and the beacon chain that agrees on them. One row is one validator at one slot, with its balance and status at that moment. uncle_blocks holds a closed chapter. Before the 2022 switch away from mining, a block produced slightly too late became an uncle, referenced by a later canonical block and rewarded in part. The table stops at 2022-09-15 because Ethereum stopped producing them.