Indexed zkSync EraBlockchain Data

zkSync Era is a validity rollup built by Matter Labs and open to general use since 2023. Batches of transactions execute off-chain, a zero-knowledge proof of that execution is produced, and a contract on Ethereum verifies it, which is what settles the batch. What reaches Ethereum is the state difference each batch produced rather than the transactions themselves. Compatibility with the EVM began at the source level: Solidity and Vyper compile to EraVM, the chain’s own virtual machine, so a contract’s source ports over while its compiled artifact does not. A later upgrade added an interpreter that runs unmodified EVM bytecode on top of EraVM, so both forms now live on one chain, each with its own rule for deriving contract addresses. Account abstraction is part of the protocol: every account can carry its own validation logic, and a paymaster can settle the fee for a transaction it did not send. Gas is paid in ETH, while ZK is a separate network token introduced in 2024.

SonarX indexes 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 activity here lines up with Ethereum and the other rollups without a per-chain translation step.

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 zkSync Era on request. Kafka streaming can be enabled for zkSync Era on request.

Two assumptions carried over from other EVM chains break here. The first is that the sender pays: with native account abstraction the fee payer, the signer and the account that acted can be three different addresses, so a wallet’s cost history is reconstructed from the transaction’s own fields rather than assumed from its sender. The second is address prediction. Contracts deployed through EraVM use a derivation Ethereum’s formula cannot reproduce, while contracts deployed through the EVM interpreter use Ethereum’s, so one chain carries two schemes and a contract map built on either alone mislabels rows quietly. Timestamps need care as well: they are not strictly increasing, so ordering by time is not ordering by block.

Account-level work dominates. Wallet analytics is the recurring request, because smart accounts make a user and an address a many-to-one relationship, and answering how many people used an application means resolving accounts rather than counting senders. DeFi position analysis is the second workload, on decoded events with internal transfers attached. Token distribution analysis is the third, following an issuance from mint through transfers, where sponsored transactions mean a holder can receive and move tokens without ever holding ETH. Teams that sponsor fees for their users have a fourth job: adding up what the paymaster spent over a campaign, which is a question about one contract’s outflows rather than about any user’s wallet. Teams comparing prover designs usually pull Scroll alongside it.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. zkSync Era history is available now, with smart-account and paymaster fields kept rather than flattened away. 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.