Indexed ArbitrumBlockchain Data

Arbitrum One is an optimistic rollup that has settled on Ethereum since 2021. A sequencer orders transactions and posts them to Ethereum in compressed batches, and withdrawals wait out a challenge window before they can be claimed on the Ethereum side, because a fraud proof has to remain possible until then. Nitro, activated on 31 August 2022, replaced the original custom VM with a Geth-based execution core compiled to WASM for the fraud prover, which is the point at which Arbitrum became bytecode-equivalent to Ethereum rather than merely compatible. Gas is paid in ETH, and ARB is a governance token that takes no part in fees. The chain keeps its own fast-moving block height while contracts that read a block number see an approximation of Ethereum’s, so two clocks run side by side. Messages arriving from Ethereum are not ordinary transactions either: they create retryable tickets that are redeemed separately. Arbitrum Nova, the AnyTrust chain that keeps its data with a committee instead of on Ethereum, is a different network.

SonarX indexes Arbitrum 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 rollup-specific record types are preserved rather than normalized away, so deposits, retryable tickets and the per-block system records stay identifiable. Everything shares the model SonarX uses across every network it covers, which is what lets an L2 question and an L1 question be answered in one query.

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 Arbitrum. Kafka streaming carries the same records as a live topic today.

The transaction set is wider here than on Ethereum, and that is where pipelines break. Deposits, retryable tickets, their redemptions and an internal transaction at the head of every block all sit beside ordinary user transactions, and none of them behave like one. Block numbering is the second trap, since the number a contract sees and the number the chain counts are different series. The third is historical: Nitro changed the execution engine in 2022, so a complete backfill covers two formats and the normalized model has to make them agree rather than presenting a seam to whoever queries it.

Arbitrum attracts the most position-level analytical work of any L2. Perpetuals and derivatives research is the first: funding, liquidations and open interest reconstructed from decoded logs, because these venues are contracts rather than exchange state. Lending and vault accounting is the second, where a position is a sequence of events and the interest accrued between them has to be derived rather than read. Third is bridge and flow analysis, following capital between Ethereum and the rollup, which needs the deposit and withdrawal records on both sides rather than a net balance change. Fee attribution runs underneath all three: the cost of a strategy here is the execution fee plus the share of the batch it caused, and a backtest that ignores the second number flatters everything it measures. DeFi analytics is the solution area this work sits in across chains.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Arbitrum 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.