Fastest Wormhole VAA finalization by source chain, live latency
BridgesScroll
No data in window
Unichain
No data in window
Unichain leads on both live benchmarks. Unichain wins on Fastest LayerZero source chain by end-to-end message delivery (37.50 s vs 3.7 min), Bridged TVL by chain ($93.61M vs $43.36M). Data as of 2026-10-06 UTC.
Native bytecode-equivalent zkEVM rollup. Sequencer cadence is prover-bound: empty periods see longer gaps between blocks while busy minutes produce blocks at a sub-3-second rate.
Scroll
No data in window
Unichain
No data in window
Scroll
No data in window
Unichain
No data in window
Scroll
Trails3.7 min
Unichain
Leads37.50 s
| Provider | Bridged TVL | Bridged share | 7d change | 7d vs peers | Native | Canonical | External |
|---|---|---|---|---|---|---|---|
| Scroll | $43.36M | 89.4% | 1.29% | - | $5.13M | $40.37M | $2.99M |
| Unichain | $93.61M | 100.0% | 4.65% | 3.32% | - | $44.79M | $48.82M |
Bridged TVL is value secured by the chain's bridge, not value locked in its DeFi protocols; a chain can rank high on one and low on the other. The split is L2Beat's: canonical is escrowed on the host chain by the chain's own contracts, external came through a third-party bridge, native was minted here. Rows are the chains L2Beat tracks in its scaling summary; a settled L1 has no row by construction, not by omission. Size is not quality: a large balance says capital came, not that it stayed.
Scroll and Unichain are compared on 4 shared OpenChainBench benchmarks. Unichain leads on Fastest LayerZero source chain by end-to-end message delivery. See the live table on this page for every metric.
On the Fastest LayerZero source chain by end-to-end message delivery benchmark, Unichain leads at 37.50 s (provisional) versus Scroll at 3.7 min (provisional). Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing; panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.