Fastest Wormhole VAA finalization by source chain, live latency
BridgesArbitrum
Trails1066.67 min
- p99
- 1772.00 s
- rank
- #13
- samples
- 28
Celo
Leads1050.00 min
- p99
- 1197.00 s
- rank
- #11
- samples
- 1
Arbitrum leads on 1 of 2 shared benchmarks, Celo on 1. Arbitrum wins on Fastest LayerZero source chain by end-to-end message delivery (27.65 s vs 47.48 s). Celo wins on Fastest Wormhole VAA finalization by source chain, live latency (1050.00 s vs 1066.67 s).
Optimistic rollup built on Nitro stack with a fast-finality sequencer. Sub-second block times (~250 ms) via a 250 ms default block interval, far below the 2 s OP Stack convention. 7-day fraud-proof window for L1 finality.
Arbitrum
Trails1066.67 min
Celo
Leads1050.00 min
Arbitrum
Trails1050.00 min
Celo
No data in window
Arbitrum
Leads27.65 s
Celo
Trails47.48 s
Arbitrum
Trails12.58 s
Celo
No data in window
Arbitrum
Trails1433.34 min
Celo
No data in window
Arbitrum and Celo are compared on 5 shared OpenChainBench benchmarks. Arbitrum leads on Fastest LayerZero source chain by end-to-end message delivery. Celo leads on Fastest Wormhole VAA finalization by source chain, live latency. See the live table on this page for every metric.
On the Fastest LayerZero source chain by end-to-end message delivery benchmark, Arbitrum leads at 27.65 s versus Celo at 47.48 s. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest Wormhole VAA finalization by source chain, live latency benchmark, Celo leads at 1050.00 s versus Arbitrum at 1066.67 s. 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.
A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.