Indexed EthereumBlockchain Data

Ethereum has produced blocks continuously since its genesis block on 30 July 2015. Since the Merge in September 2022 it has run on proof of stake under Gasper, which pairs Casper FFG for finality with LMD-GHOST for fork choice: validators propose one block per twelve-second slot, thirty-two slots make an epoch, and a block is finalized once two consecutive epochs are justified, roughly thirteen minutes after it is produced. Consensus itself lives on a separate chain, indexed as Ethereum Beacon Chain. Execution happens in the Ethereum Virtual Machine against an account model rather than a UTXO set, so every twenty-byte address carries a balance, a nonce and, for contracts, code and storage. The native asset is ETH, divisible to eighteen decimals and metered in gwei. Two later changes shape the data: EIP-1559 in August 2021 burned the base fee instead of paying it to the block proposer, and the Dencun upgrade of March 2024 moved rollup data into blobs that the consensus layer stores apart from calldata.

SonarX indexes Ethereum end to end: blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so an Ethereum query and a Base query take the same shape and can be joined without a translation layer.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery keeps the same dataset current to chain tip. Point-in-time balance tables, the real-time balances API and the batch wallets, tokens and balances API are all available for Ethereum. Kafka streaming carries the same records as a live topic today.

Two properties make Ethereum harder than its size suggests. Since the Merge it is effectively two chains: withdrawals and validator rewards are recorded on the consensus layer, so a complete ETH flow for a staking address is not visible from execution data alone. And much of what analysts want is not in the block. Internal transfers exist only in traces, which have to be produced by re-executing each transaction, and a decoded log is only as reliable as the ABI resolution behind it, which for proxy contracts means following the implementation, not the emitting address. Blob data adds a deadline: consensus clients prune blobs after roughly eighteen days, so those records are captured as they arrive or not at all.

Three workloads account for most Ethereum requests SonarX receives. Portfolio reconstruction and fund accounting need a wallet’s holdings as at a specific block or timestamp, reconciled against transfers rather than inferred from a current snapshot, which is what point-in-time balances exist for. Position-level DeFi analytics need decoded logs and traces together, because a lending position is a sequence of events and the true cost of a swap is only visible once internal transfers are attached to it. Rollup cost accounting is the newer one: since Dencun, an L2’s operating cost is a blob-fee series on Ethereum, which makes L1 data the ledger for L2 economics.

Transaction monitoring, treasury reporting and token distribution work sit on the same indexed tables. SonarX maintains the data; the analysis stays yours.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Ethereum history and the balance APIs are available now, so a first delivery is provisioning rather than engineering. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.