Indexed ScrollBlockchain Data

Scroll is a zero-knowledge rollup that has been producing mainnet blocks since 2023. A sequencer orders transactions, a prover generates a validity proof for each batch, and a contract on Ethereum verifies that proof, which is what makes the batch final. There is no challenge window, because correctness is proved rather than assumed. The chain’s distinguishing choice is equivalence: its zkEVM proves Ethereum bytecode itself instead of a compiled alternative, so contracts, twenty-byte addresses, opcodes and developer tooling behave as they do on L1 and the same compiled artifact can be deployed to both. Gas is paid in ETH, with SCR a separate governance token that buys no block space. Transactions that start on Ethereum, such as bridge deposits, are delivered into Scroll blocks as messages, which is why some transactions in a block have no ordinary sender paying for them.

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 a contract deployed to both Scroll and Ethereum can be analyzed as one deployment across two networks.

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

Bytecode equivalence removes one problem and two chain behaviors add others. Because the same artifact runs on both networks, an ABI resolved on Ethereum decodes the identical contract here, so logs are readable without a second registry and proxy resolution follows the same rules. Transactions delivered from Ethereum are harder: they execute inside L2 blocks as their own transaction type, with no sender paying an L2 fee, so per-transaction fee statistics have to exclude them, and tracing a deposit means joining an L1 message to its L2 execution. Timestamps are the other trap. They are not strictly increasing, and consecutive blocks can share a second, so ordering by time is not ordering by block.

Bridge accounting is the workload that comes up first. Assets arrive from Ethereum and leave the same way, and stating what is actually held on the rollup at a point in time means matching both legs rather than trusting a bridge contract’s balance. Position-level DeFi analytics is the second, and it is cheap to extend here because the same decoding that works on L1 works unchanged. Deployment comparison is the third: protocol teams running the same contracts on Ethereum and on Linea or Scroll want user behavior and cost per action side by side, which only works when all three histories sit in one place. Proving economics is a fourth: each batch records what was proven and when it was verified, which is the raw material for comparing one rollup’s settlement costs against another’s.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Scroll history is available now, including the L1 messages that execute inside its blocks. 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.