Cardano Mempool Tracker & Congestion Monitor

The Mempool (Memory Pool) holds all valid unconfirmed transactions waiting to be included in an upcoming block by a slot leader. Monitoring mempool size, transaction composition, and block body capacity provides real-time visibility into Cardano's deterministic network utilization.

Live Mempool Queue
0 txs
Instant Clearance (< 20s)
Mean Throughput (24h)
-- TPS
Network Velocity (24h)
Mean Tx Fee (24h)
-- ADA
Deterministic Base Fee
Block Space Saturation
--
vs 90 kB Max Block Body
Plutus Script Share
--
Smart Contract Execution

eUTXO Transaction-Mix Matrix

Live Traffic Breakdown

Cardano transactions are categorized by their deterministic payload. Unlike account-based chains, multiple contract interactions, multi-asset token mints, and pure Lovelace transfers execute with exact predictable fees.

Simple ADA Transfers 42.5%
Plutus Smart Contracts 31.8%
Native Assets & Mints 18.2%
Governance & Staking 7.5%

Live Block Space & Mempool Drain Feed (Recent Blocks)

Real-time Mempool Clearance

Real-time log of recently observed blocks demonstrating how many unconfirmed transactions were cleared from the mempool buffer, total block size saturation, script execution memory units, and fee yield. Click any SPO to view complete stake pool telemetry.

Block / Slot Slot Leader (SPO) Cleared Txs Block Size & Saturation Script Memory Block Fees Congestion State
Connecting to Cardano live mempool telemetry...

Cardano eUTXO Mempool Architecture

Cardano uses the extended UTXO (eUTXO) deterministic accounting model. Transactions specify exact input UTXOs and output UTXOs along with fee parameters:

  • Deterministic Fees: Transaction fees on Cardano are calculated deterministically from byte size ($a \cdot \text{size} + b$) plus exact Plutus script execution units ($\text{price}_{\text{mem}} \cdot \text{mem} + \text{price}_{\text{step}} \cdot \text{steps}$).
  • No Priority Bidding Warfare: Unlike account-based blockchains, Cardano transactions do not suffer from unpredictable gas bidding spikes during high traffic.
  • Mempool Capacity: Nodes enforce maximum mempool byte limits (defaulting to $2 \times \text{maxBlockBodySize} = 176\text{ KiB}$). When traffic spikes occur, transactions queue up predictably in mempool buffers.