Fastest Wormhole VAA finalization by source chain, live latency
BridgesMantle
No data in window
Monad
Trails3.83 s
- rank
- #4
- samples
- 33provisional
Monad leads on both live benchmarks. Monad wins on Fastest Chainlink CCIP source chain by end-to-end delivery latency (46.03 s vs 25.0 min), Fastest LayerZero source chain by end-to-end message delivery (48.46 s vs 1.4 min). Data as of 2026-10-24 UTC.
Modular OP Stack fork using EigenDA for data availability rather than Ethereum calldata, cutting L1 anchoring cost. 2-second sequencer block time, MNT token for gas (ETH-pegged).
Mantle
No data in window
Monad
Trails3.83 s
Mantle
Trails25.0 min
Monad
Leads46.03 s
Mantle
Trails1.4 min
Monad
Leads48.46 s
| Provider | 30d change | Stablecoin float | Net 7d | 7d change |
|---|---|---|---|---|
| Mantle | - | $548.86M | $13.05M | 2.44% |
| Monad | - | $690.41M | - | - |
Stablecoin float is where dollars are parked, not what they do. A chain can take in a billion that sits idle, and lose float to a single issuer redeeming. The figure is DefiLlama's chain-wide pegged-USD aggregate, every issuer combined; it does not separate a bridge inflow from a native mint, and a dollar bridged to an L2 counts on both chains, so rows are not additive. Read the net dollars with the percentage beside them: the same $400M is a rounding error on Ethereum and a doubling elsewhere.
Mantle and Monad are compared on 4 shared OpenChainBench benchmarks. Mantle leads on Stablecoin flow by chain. Monad leads on Fastest Chainlink CCIP source chain by end-to-end delivery latency. See the live table on this page for every metric.
On the Stablecoin flow by chain benchmark, Mantle leads at -$206.4K versus Monad at -$6.25M. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest Chainlink CCIP source chain by end-to-end delivery latency benchmark, Monad leads at 46.03 s (provisional) versus Mantle at 25.0 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.