Fastest median, zk rollups
hoursThe shortest median time from withdrawal to earliest finalization among covered zk rollups over the last 30 days, with the rollup named.
How long does a native withdrawal from each layer 2 to Ethereum take right now?
How long a native withdrawal from each rollup to Ethereum takes, from the layer 2 transaction to the moment it can be finalized.
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.
How long native withdrawals take on each covered rollup over the last 30 days.
The shortest median time from withdrawal to earliest finalization among covered zk rollups over the last 30 days, with the rollup named.
The median time from withdrawal to earliest finalization across covered optimistic rollups over the last 30 days.
The median time between when withdrawals could first be finalized and when users finalized them, across covered rollups.
Withdrawals started on covered rollups and not yet finalized on Ethereum at the latest read.
For each rollup: proof system, median and slowest-tenth time to earliest finalization, median observed time and the step that takes longest.
How withdrawal times and proving cadence have moved over time.
The median time between consecutive proofs verified on Ethereum, across covered zk rollups over the selected period.
The median time between state proposals on Ethereum, across covered optimistic rollups over the selected period.
Native withdrawals finalized on Ethereum each week, by rollup.
The weekly median time from withdrawal to earliest finalization for each rollup over the selected period.
A native withdrawal moves assets from a rollup back to Ethereum through its canonical bridge, and it cannot be released until Ethereum accepts the rollup's state. How long that takes depends on the proof system. This dashboard measures it from the chains themselves for every covered rollup: the time from the withdrawal transaction on the layer 2 to the first moment it could be finalized on Ethereum and to the moment users actually finalized it.
On optimistic rollups such as Base, OP Mainnet and Arbitrum One, a withdrawal waits through a challenge window of about a week after the state that includes it is proposed. On zk rollups such as ZKsync Era, Linea, Scroll and Starknet, it waits for a validity proof of its batch to be verified, which depends on how often each rollup proves. Both are timed here step by step.
Users often finalize later than they could, so the dashboard keeps two clocks: the protocol's minimum and the observed time. Fast bridges and intent networks can return funds sooner for a fee; they are outside this dashboard, which measures the native route.
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 →Read from chain state and history
On Base, a native withdrawal is proven on Ethereum once a state proposal covers it and can be finalized after the proof system's waiting period, about a week under fault proofs. The dashboard shows the current median for each step and marks any change to Base's proof system.
The waiting period gives anyone time to challenge a wrong state claim before Ethereum treats it as final. A shorter window would leave less time to catch a fraudulent withdrawal, so most optimistic rollups keep it at about a week.
No. They wait until a validity proof for their batch is verified on Ethereum, and some rollups add an execution delay after that. How often a rollup proves sets the wait, which the dashboard measures for each one.
A withdrawal from Arbitrum One can be executed on Ethereum once the assertion that includes it is confirmed, after a challenge period of about a week under the BoLD protocol, and the user then executes it from the outbox. The dashboard times both steps.
Fast bridges and intent networks pay out on Ethereum much sooner and carry the native withdrawal's wait and risk themselves, for a fee. This dashboard measures the native route only; the cross-chain intents dashboard covers fill times.
Deposits from Ethereum and withdrawals back through each layer 2's canonical bridge, by chain and token, with the net flow per day.
EthereumBaseArbitrum+9For each rollup: who can upgrade its bridge contracts, how many signers must agree, how long upgrades wait and whether users can exit first.
EthereumBaseArbitrum+11How much volume intent-based bridges and swaps fill, which solvers and relayers fill it and how long a fill takes from deposit to delivery.
Multi-chainEthereumBase+2Gas, transactions and active addresses on Arbitrum One, with the DAO's ordering revenue from Timeboost auctions and priority fees.
ArbitrumEthereumEvery covered Ethereum layer 2 in one sortable table: transactions, active addresses, user fees, costs paid to Ethereum and value secured.
Multi-chainEthereumBase+7Transactions 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.