Cheapest blockchain transaction fee, live across 15 L1 and L2 chains
BlockchainsEthereum
Trails$0.00750
- p99
- $0.6232
- rank
- #10
- samples
- 20,159
Mantle
Leads$0.000575
- p99
- $0.00346
- rank
- #5
- samples
- 20,159
Ethereum leads on 1 of 3 shared benchmarks, Mantle on 2. Ethereum wins on Fastest Chainlink CCIP source chain by end-to-end delivery latency (17.1 min vs 25.0 min). Mantle wins on Cheapest blockchain transaction fee, live across 15 L1 and L2 chains ($0.000575 vs $0.00750), Fastest LayerZero source chain by end-to-end message delivery (1.0 min vs 4.1 min).
PoS chain using Gasper (Casper FFG plus LMD-GHOST). 12-second slots with deterministic finality every two epochs, roughly 12.8 minutes.
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).
Ethereum
Trails$0.00750
Mantle
Leads$0.000575
Ethereum
Trails14.5 min
Mantle
No data in window
Ethereum
Leads17.1 min
Mantle
Trails25.0 min
Ethereum
Trails4.1 min
Mantle
Leads1.0 min
Ethereum
Trails16.9 min
Mantle
No data in window
Ethereum and Mantle are compared on 5 shared OpenChainBench benchmarks. Ethereum leads on Fastest Chainlink CCIP source chain by end-to-end delivery latency. Mantle leads on Cheapest blockchain transaction fee, live across 15 L1 and L2 chains. See the live table on this page for every metric.
On the Fastest Chainlink CCIP source chain by end-to-end delivery latency benchmark, Ethereum leads at 17.1 min versus Mantle at 25.0 min (provisional). Live measurement is updated continuously by the OpenChainBench harness.
On the Cheapest blockchain transaction fee, live across 15 L1 and L2 chains benchmark, Mantle leads at $0.000575 versus Ethereum at $0.00750. 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.