Fastest Wormhole VAA finalization by source chain, live latency
BridgesCelo
Trails17.5 min
- rank
- #11
- samples
- 2provisional
Scroll
No data in window
Split decision: Celo leads on Fastest LayerZero source chain by end-to-end message delivery (15.00 s vs 4.3 min); Scroll leads on Bridged TVL by chain ($34.44M vs $16.51M). Data as of 2026-10-24 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.
Celo
Trails17.5 min
Scroll
No data in window
Celo
No data in window
Scroll
No data in window
Celo
Leads15.00 s
Scroll
Trails4.3 min
Celo
Trails25.0 min
Scroll
No data in window
| Provider | Bridged TVL | Bridged share | 7d change | 7d vs peers | Native | Canonical | External |
|---|---|---|---|---|---|---|---|
| Celo | $16.51M | 6.11% | - | 2.93% | $253.75M | $2.12M | $14.39M |
| Scroll | $34.44M | 90.1% | - | - | $3.78M | $31.85M | $2.59M |
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.
Celo and Scroll are compared on 5 shared OpenChainBench benchmarks. Celo leads on Fastest LayerZero source chain by end-to-end message delivery. Scroll leads on Bridged TVL by chain. See the live table on this page for every metric.
On the Fastest LayerZero source chain by end-to-end message delivery benchmark, Celo leads at 15.00 s (provisional) versus Scroll at 4.3 min (provisional). Live measurement is updated continuously by the OpenChainBench harness.
On the Bridged TVL by chain benchmark, Scroll leads at $34.44M versus Celo at $16.51M. 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.