BetaThis app is under active development. Features may change or break.Share Feedback →

What is Monad Blockchain?

Learn about Monad, the high-performance EVM-compatible Layer 1 blockchain achieving 10,000 TPS with parallel execution, MonadBFT consensus, and sub-second finality.

Overview

Monad is a high-performance, EVM-compatible Layer 1 blockchain that achieves unprecedented throughput through architectural innovations in consensus, execution, and storage — while maintaining full compatibility with Ethereum's tooling and smart contracts.

Unlike chains that sacrifice compatibility for speed, Monad delivers 10,000 transactions per second with sub-second finality while remaining fully compatible with existing Ethereum bytecode, wallets, and developer tools. This means any Solidity smart contract can be deployed on Monad without modification.

Key Metrics

10,000 TPS

Throughput

400ms

Block Time

800ms

Finality

MON

Native Token

Mainnet Live

Monad mainnet launched on November 24, 2025. The native token is MON and the chain ID is 10150.

Core Innovations

Monad's performance comes from four key innovations that work together to maximize throughput without compromising security or decentralization:

MonadBFT Consensus

MonadBFT is a pipelined Byzantine Fault Tolerant consensus protocol derived from HotStuff. It overlaps the proposal, voting, and certification phases so that at any given round, the network is simultaneously proposing a new block, voting on the previous one, and finalizing the one before that.

  • 400ms block times with 800ms full finality (400ms speculative finality)
  • Linear communication complexity — O(n) instead of O(n²), supporting 100-200+ validators
  • Tail-fork resistance — a novel improvement over standard HotStuff that prevents chain history from being overwritten when leaders miss their turn
  • Stake-weighted, deterministic leader election with 50,000-block epochs (~5.5 hours)

Parallel Execution

Instead of processing transactions one-by-one like Ethereum, Monad executes transactions in parallel using optimistic concurrency control (OCC):

  1. Optimistic Execution — Transactions begin processing before earlier ones complete, assuming no conflicts. Each produces a "PendingResult" recording inputs and outputs.
  2. Conflict Detection — After parallel execution, the system checks each PendingResult serially. If inputs are still valid, outputs are applied. If state changed, the transaction is re-executed.
  3. Re-execution Optimization — When re-execution is needed, expensive work (signature recovery, cached state) is preserved — only state-dependent computation reruns.

Deterministic Results

Parallel execution is an internal optimization only. Monad blocks are identical to Ethereum blocks — linearly ordered transactions with deterministic final state. Developers don't need to change anything.

MonadDB Storage

MonadDB is a custom storage engine designed specifically for EVM parallel processing. Unlike Ethereum's LevelDB-based approach, MonadDB implements a native Merkle Patricia Trie that significantly reduces disk I/O and supports concurrent data requests needed for parallel execution.

  • Native Merkle Patricia Trie implementation
  • Reduced disk I/O compared to LevelDB approach
  • Concurrent data request support for parallel execution
  • State sync via snapshots verified against on-chain Merkle roots

RaptorCast Propagation

RaptorCast uses erasure-coded block chunks distributed via a two-level broadcast tree. This approach reduces latency and bandwidth usage compared to traditional gossip protocols, enabling faster block propagation across the validator network.

EVM Compatibility

Monad maintains full bytecode compatibility with Ethereum (Pectra fork):

FeatureDetail
OpcodesAll supported with identical pricing
Contract Size128 KB (vs 24.5 KB on Ethereum)
TX Types0, 1, 2, and 4 (including EIP-7702)
Precompiles0x01 to 0x11 plus 0x0100 (EIP-7951)
WalletsMetaMask, Phantom — just change RPC/Chain ID

How Monad Differs from Ethereum

AspectEthereumMonad
Throughput~15 TPS10,000 TPS
Block Time12 seconds400ms
Finality~15 minutes800ms
ExecutionSequentialParallel (OCC)
ConsensusGasper (PoS)MonadBFT (pipelined BFT)
StorageLevelDBMonadDB (native MPT)
Gas ChargingActual usageGas limit (DoS prevention)
CompatibilityNativeFull bytecode compatible

Frequently Asked Questions

Does parallel execution change transaction semantics?
No. Monad blocks are identical to Ethereum blocks — linearly ordered transactions. Parallelism is an internal optimization; the final state is identical to serial execution.
When do conflicts occur in parallel execution?
When multiple transactions access the same state (storage slot, account balance). For example, two transactions both trying to transfer from the same wallet.
Is my Ethereum smart contract compatible with Monad?
Yes. Deploy the same bytecode with no code changes needed — just point to a different RPC endpoint.
What is speculative finality?
After 400ms (1 block), state is very likely final. After 800ms (2 blocks), state is fully confirmed. Most dApps can safely assume 400ms finality.
How does Monad achieve 10,000 TPS?
Through the combination of MonadBFT pipelined consensus (400ms blocks), parallel execution (OCC), MonadDB (native MPT storage), and RaptorCast (erasure-coded block propagation).

Getting Started

Ready to explore Monad? Here are some next steps:

NextMON Token