Indexed BlastBlockchain Data

Blast is an Ethereum Layer 2 that started producing blocks in February 2024, built as a fork of the OP Stack. It is an optimistic rollup: a sequencer orders transactions into two-second blocks and posts the data to Ethereum, which settles the chain. Execution is the EVM, so addresses, contracts and tooling behave as they do elsewhere. What is not ordinary is the asset model. ETH held on Blast rebases, with the yield sourced from staking on Ethereum, and USDB, the network’s stablecoin, rebases from Treasury-bill yield, so a balance grows without any transfer being recorded. Gas is paid in ETH; BLAST, introduced in 2024, is a separate token and pays for nothing. Contracts can also claim back the gas fees their users spend, so fee revenue is not automatically the sequencer’s. The launch was unusual too: deposits opened on Ethereum in November 2023 and stayed locked there until the chain existed.

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 Blast positions can be compared with the same wallets elsewhere without a translation step.

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 Blast, and the rest can be enabled on request. Kafka streaming can be enabled for Blast on request.

Balances here move without transfers. Yield is rebased into the balance itself, for native ETH and for the rebasing token contracts alike, so no event marks the change. The standard method of replaying transfer logs to reconstruct a holding, which is correct on every ordinary EVM chain, drifts on this one, and the drift widens the longer the window. SonarX derives positions from chain state instead. Yield configuration adds a second wrinkle: accounts and contracts do not default to the same mode, so two addresses holding the same asset can accrue differently, and that setting is part of the record rather than a property of the token.

Yield accounting is the workload unique to this chain. Splitting a balance change into what was transferred and what accrued is the first question a fund or an auditor asks here, and it cannot be answered from transfers alone. Position-level DeFi analytics is the second, since protocols built on a rebasing asset have to treat the asset’s own growth as part of a position’s return. Application revenue is the third: teams that claim the gas fees their users pay need those claims reconciled against what was spent, which is the same shape of question that Mantle raises with its own fee token. Anyone modeling the network’s economics needs that split at the aggregate level, since what the sequencer keeps depends on how much was claimed back. A treasury holding rebasing assets reports the same split, period by period.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Blast history is available now, with positions derived from state rather than from transfer arithmetic. 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.