Indexed UnichainBlockchain Data

Unichain is an Ethereum Layer 2 built by Uniswap Labs on the OP Stack, opened to the public in February 2025 after producing its first blocks in late 2024. It is an optimistic rollup with permissionless fault proofs, settling to Ethereum, where its batch data is posted as blobs. Blocks arrive every second. Inside each one the builder publishes Flashblocks: partial blocks issued several times a second as preconfirmations, which are not canonical blocks and carry no block number of their own. Block building itself runs inside a trusted execution environment kept separate from the sequencer. Execution is the EVM, with ordinary twenty-byte addresses. Gas is paid in ETH, while UNI is Uniswap’s governance token on Ethereum and pays for nothing here. The workload the chain was built around is Uniswap v4, where every pool is state inside one contract rather than a deployment of its own.

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 trading on Unichain can be compared with the same protocol’s deployments elsewhere without reconciling two schemas.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. The real-time balances API and the batch wallets, tokens and balances API are available for Unichain, and the rest can be enabled on request. Kafka streaming can be enabled for Unichain on request.

Two habits from other EVM chains fail here. The first is treating everything the sequencer emits as a block: Flashblocks are preconfirmations with a position inside the block being built, not entries in the chain, and only the one-second block is settled, so SonarX indexes canonical blocks and a transaction lands once. The second is keying pools by contract address. Uniswap v4 holds every pool as state in a single manager, so swaps arrive as events from one address carrying a pool identifier, and the per-pool address older pipelines join on does not exist. Netting makes it worse: a transaction moves only its net balance, so transfer records understate the trading that produced them.

Market-structure research is the first workload and the most chain-specific: pool-level behavior under v4, how hooks change execution, and how one-second blocks and sub-second preconfirmations affect where trades land in a block. Liquidity accounting is the second, reconstructing what a position earned over time when the position is state inside a manager contract rather than a balance in a pool. Flow reconciliation is the third, following assets between Ethereum, Ink and the other rollups where the same protocols are deployed. DeFi analytics work spans all three, and none of it needs a live lookup: it is range queries over a full history, run once a quarter or once a day rather than once a second.

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 as a share or a file delivery, canonical blocks only, so nothing has to be de-duplicated afterwards. 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.