Indexed Ethereum ClassicBlockchain Data

Ethereum Classic is the continuation of the chain Ethereum started. Both networks share every block from the genesis of 30 July 2015 up to block 1,920,000, where the fork of 20 July 2016 moved the DAO contract’s funds on one side and left them untouched on the other. Ethereum Classic is the side that left them, and it has stayed on proof of work since, mining under Etchash after the Thanos upgrade of November 2020 changed the hashing parameters so smaller graphics cards could keep working. The native asset is ETC, under a fixed monetary policy that cuts the block reward by a fifth every five million blocks and caps issuance near 210.7 million. Execution is the EVM, so accounts, twenty-byte addresses, Solidity contracts and event logs all behave as an Ethereum engineer expects. Transactions are signed against chain ID 61, which is what stops one network’s transaction from replaying on the other.

SonarX indexes blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, uncle records, and token transfers and balances. The same normalized model is used on every chain SonarX covers, so an address can be examined on both networks in one query rather than in two pipelines reconciled afterwards.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Balance tables and the balance APIs can be enabled for Ethereum Classic on request. Kafka streaming can be enabled for Ethereum Classic on request.

The shared prefix is the trap. Blocks 0 through 1,920,000 exist on both networks with the same hashes, so a naive join on transaction hash or address silently mixes two chains, and any statement about early activity has to be attributed to the period before the split rather than to one network. After that point the EVMs drift: Ethereum Classic adopts opcode changes through its own upgrade sequence, so a contract compiled for a newer Ethereum target can fail here, and the fee fields are the older shape because the 2021 fee market was never adopted. Uncles still exist and still pay, which post-merge Ethereum tooling no longer expects.

Two kinds of work bring teams here. The first is accounting for a listed asset: exchanges and custodians hold ETC alongside ETH, and restating a position means keeping the two chains’ records apart even where the addresses look identical. The second is proof-of-work research. Ethereum Classic is one of the few EVM chains still mined, so it carries coinbase payments, uncle rewards and difficulty history for a live Ethash-family network long after Ethereum stopped producing them, which makes it a usable control for miner-behavior research. Contract-level comparison is a third: the same Solidity source deployed to both networks executes against different opcode sets, and the traces show where. Wallet analytics covers the address-level side of this across chains, and Ethereum Beacon Chain is where the other network’s validator records live.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. History is available now, and it helps to say at the start whether Ethereum records are in scope too, since the shared prefix has to be handled deliberately. 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.