Data posted
MBBlob bytes named in EigenDA certificates posted in the selected period, in megabytes.
Which rollups use EigenDA, how much data do they post and how much restaked stake secures it?
Rollups posting to EigenDA and the data and payments behind them, with the operators and restaked stake that secure each quorum.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Rollups posting to EigenDA, their data and their payments.
Blob bytes named in EigenDA certificates posted in the selected period, in megabytes.
Rollups that posted at least one EigenDA certificate in the selected period.
ETH deposited to the payment vault for on-demand use in the period, shown beside active reservations.
EigenDA certificates posted to rollup batch inboxes on the latest complete day.
Megabytes named in certificates each day, split by rollup.
Each rollup's certificates, data posted, share of all EigenDA data and payment arrangement over the period.
Who secures EigenDA, and with how much stake in each quorum.
Operators registered to at least one EigenDA quorum at the latest day's end.
Restaked ETH and EIGEN held by operators in EigenDA's quorums at the latest day's end, each shown in its own unit.
Stake each of the largest operators holds in the ETH quorum, with its share of the quorum.
Each operator's quorums, its stake in each, its share of each quorum and the date it registered.
EigenDA is a data availability service built on EigenLayer. Rollups send their batches to EigenDA, whose operators store erasure-coded pieces and sign that the data is available, and the rollup then posts a short certificate instead of the data itself. Operators are restakers who serve one or more quorums, each backed by a different asset, such as restaked ETH or EIGEN.
This dashboard reads what EigenDA leaves on Ethereum and on the rollups that use it: operator registrations and stake by quorum, payments to EigenDA's payment vault and the certificates rollups post, each naming a blob and its size. Celo's layer 2, for example, posts to EigenDA V2, which arrived in 2025 with faster confirmation and payments through reservations and on-demand deposits.
Figures that need the disperser's own records rather than chain data are marked as off-chain, with their source. Everything else is pinned to the Ethereum or rollup block it was read at, so each figure can be checked again.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →Chain data, with some off-chain sources
A data availability service for rollups, secured by stake restaked through EigenLayer. Operators store erasure-coded chunks of each blob and attest that it is available, and rollups post a compact certificate of that attestation instead of the full data.
By operators who register for quorums and hold restaked stake in them, such as restaked ETH or EIGEN. A blob is accepted when operators holding enough of each required quorum's stake have signed for it, so the stake behind each quorum is the measure of its economic security.
Any rollup whose batches carry EigenDA certificates appears on the dashboard, identified from its batch inbox. Celo's layer 2, for example, uses EigenDA V2. The list is read from the chain, so new users show up as soon as they post.
V2, also called Blazar, cut the time to confirm that data is available from minutes to under a minute for rollups that adopt its recommended integration, and it introduced payments through reservations and on-demand deposits.
Ethereum blobs are stored and checked by Ethereum's own validators for a limited window. EigenDA relies on its own operator set and the stake restaked to it, so a rollup trades Ethereum's validator guarantee for more capacity at a different cost.
Assets restaked on EigenLayer by strategy, the operators they are delegated to, the AVSs those operators secure and each slashing event.
EthereumData each rollup posts to Celestia, the TIA it pays, how full blocks are and the cost per megabyte beside Ethereum blobs.
Multi-chainEthereumBlob base fee and blobs per block against the target and maximum, with the rollups that buy blob space, block by block on Ethereum.
EthereumFees each Ethereum layer 2 collects from users against what it pays Ethereum for data and proofs, with the margin left, by day and chain.
Multi-chainBaseArbitrum+5Whether weETH, rsETH, ezETH and other liquid restaking tokens hold the assets they claim, where that backing sits and how rates moved.
EthereumArbitrumBase+1Transactions and gas per second on Ethereum and each layer 2, in total and per chain, counted from blocks without system transactions.
Multi-chainEthereumBase+6Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.