Fastest LayerZero source chain by end-to-end message delivery
Monad leads layerzero delivery at 22.60 s (p50, 24h) on Fastest LayerZero source chain by end-to-end message delivery. Wall-clock seconds from source-chain transaction to destination-chain execution for a LayerZero message, measured across LayerZero source chains via the public layerzero-scan feed.
TL;DR. As of , Monad leads layerzero delivery at 22.60 s (p50, 24h) on Fastest LayerZero source chain by end-to-end message delivery. Source: OpenChainBench, https://openchainbench.com/benchmarks/layerzero-message-latency.
LayerZero is a cross-chain messaging network built on a configurable Decentralized Verifier Network (DVN) stack. When a transaction on a source chain emits a LayerZero message, the application-selected DVNs each verify the source block, the application-selected Executor then delivers the message on the destination chain. This benchmark measures end-to-end message delivery latency by source chain: wall-clock seconds from the source-tx block timestamp to the destination-tx block timestamp for every DELIVERED message returned by layerzero-scan. Every value on this page is an observation of real user traffic (Stargate, LayerZero-native applications, cross-chain token bridges), never a canary transaction. Latency distribution reflects the combined DVN verification time + Executor delivery time + destination block inclusion. Sub-second BFT source chains (BNB, Sui) minimize the observation floor; L1s with longer block times (Ethereum ~12s) inherit that floor before DVN work even begins.
Methodology
For each LayerZero-supported source chain with non-trivial mainnet traffic, we measure the wall-clock latency between a source-chain transaction and destination-chain execution. Data source: the public `https://scan.layerzero-api.com/v1/messages/latest` feed, polled every 60 seconds with two pages of 150 messages each. Each DELIVERED message's `destination.blockTimestamp - source.blockTimestamp` is one observation of end-to-end latency, recorded in a per-source-chain histogram. The p50/p90/p99 shown here are computed via Prometheus `histogram_quantile` over the last 24 hours. See cross-chain-messaging-latency for the side-by-side comparison across all four end-to-end protocols on the same shared observation stack.
Frequently asked
What is LayerZero?
LayerZero is a cross-chain messaging network built on a configurable DVN (Decentralized Verifier Network) stack. Applications choose which DVNs verify their messages and which Executor delivers them, so the security model is application-defined rather than a single global consensus like Wormhole or CCIP.
What does this benchmark measure?
Wall-clock seconds from a source-chain transaction to destination-chain execution for LayerZero messages that reached DELIVERED status. It is a passive measurement of real user traffic , every observation is a LayerZero message a real user or protocol actually sent.
Why do some source chains have huge tails?
Two causes typically. First, some source chains have long block times (Ethereum ~12s), which sets a floor before DVN work even begins. Second, the DVN + Executor pair the application selects can be slow if it is a low-liquidity or under-resourced set , this is a choice the application makes, not a property of LayerZero itself.
How does the data get sourced?
The harness polls the public `https://scan.layerzero-api.com/v1/messages/latest` endpoint every 60 seconds and records `destination.blockTimestamp - source.blockTimestamp` for each new DELIVERED message. The endpoint is LayerZero's own scan API , no auth required. No canary transactions are sent, no user funds are used.
Which source chain is fastest for LayerZero today?
Monad currently leads at 22.60 s (p50 over the last 24 hours). The leaderboard re-sorts continuously against fresh Prometheus samples; the ranking on this page is the ranking right now.
Can I compare this to the Chainlink CCIP or Wormhole bench?
Only carefully. LayerZero DVNs sign pre-finality by default; CCIP waits for source-chain finality before its DON commits; Wormhole Guardians sign a VAA that a relayer then delivers separately. Each protocol measures a slightly different thing when you look at end-to-end wall-clock. The cross-chain messaging comparison meta-bench exposes a finality-normalized column so DVN+Executor work can be compared to CCIP's DON+execution work directly.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/layerzero-message-latency