Network Congestion

What Is Network Congestion?

Network congestion is the state in which a blockchain receives more transactions than it can include in the next block. Every blockchain has a finite processing capacity: Bitcoin produces one block roughly every 10 minutes with a maximum weight of 4 million weight units, and Ethereum targets one block every 12 seconds with a gas limit per block. When incoming transaction volume exceeds these limits, a backlog forms.

The effect is similar to a highway at rush hour. The road has a fixed number of lanes, and when more cars want to use it than can fit, traffic slows down and drivers sit in queues. On a blockchain, the "lanes" are block space, the "cars" are transactions, and the "toll" is the transaction fee. Users who pay higher fees get priority, while lower-fee transactions wait in the mempool for minutes, hours, or even days.

How It Works

Congestion follows a predictable cycle driven by supply and demand for block space. The supply side is fixed by protocol rules, while the demand side fluctuates with user activity.

The Congestion Cycle

1. A surge in activity occurs: a popular token launch, an NFT mint, a protocol upgrade, or a market-moving event drives users to submit transactions
2. Incoming transactions exceed block capacity, and the mempool begins to grow
3. Miners (or validators) select the highest-fee transactions first, creating a competitive fee market auction
4. Users who need fast confirmation raise their fee rates, pushing fees higher across the board
5. Lower-fee transactions are displaced further back in the queue, some falling below the mempool policy minimum and being dropped entirely
6. Activity eventually subsides, the mempool drains, and fees return to baseline

Bitcoin Congestion Mechanics

Bitcoin's congestion dynamics are shaped by its SegWit block weight system. Each block is limited to 4 million weight units, where non-witness data costs 4 weight units per byte and witness data costs 1 weight unit per byte. In practice, a typical block holds about 2,000 to 4,000 transactions depending on their complexity.

When blocks are consistently full, unconfirmed transactions accumulate in the mempool. Fee estimation algorithms analyze this backlog to recommend appropriate fee rates. During severe congestion, the mempool can swell to hundreds of megabytes and contain hundreds of thousands of unconfirmed transactions.

# Check mempool size and fee estimates via Bitcoin Core RPC
bitcoin-cli getmempoolinfo
# Returns: size (tx count), bytes, usage, maxmempool, ...

bitcoin-cli estimatesmartfee 6
# Returns estimated fee rate (BTC/kvB) for confirmation within 6 blocks

bitcoin-cli getmempoolentry <txid>
# Check a specific transaction's position and fee rate

Ethereum Congestion and EIP-1559

Ethereum handles congestion differently through EIP-1559, activated in August 2021 with the London hard fork. Instead of a pure auction, Ethereum uses a protocol-set base fee that adjusts algorithmically based on block utilization:

• When a block is more than 50% full, the base fee increases by up to 12.5% for the next block
• When utilization drops below 50%, the base fee decreases by up to 12.5%
• Users add a priority fee (tip) on top of the base fee to incentivize faster inclusion
• The base fee is burned rather than paid to validators, reducing ETH supply during high activity

This mechanism makes fee movements more predictable: instead of chaotic spikes where gas prices could jump from 20 gwei to 200 gwei in minutes (as happened pre-EIP-1559), fees now adjust gradually block by block. However, during sustained congestion, the base fee still rises significantly as blocks remain full.

Historical Congestion Events

Several major events illustrate how congestion impacts fees and user experience. For a deeper analysis, see the mempool congestion economics research article.

Bitcoin Fee Spikes

The April 2024 Runes launch at block 840,000 produced the highest fees in Bitcoin's history, with priority transactions reaching 2,750 sat/vB. Total Bitcoin transaction fees in 2023 reached 23,445 BTC, more than four times the 5,375 BTC paid in 2022, driven largely by inscription activity.

Ethereum Gas Spikes

Before EIP-1559, gas prices regularly spiked during high-demand events. DeFi summer (2020) and the NFT boom (2021) pushed gas prices above 200 gwei, making simple transfers cost $50 or more. After EIP-1559 and the shift to proof of stake, combined with Layer 2 adoption, mainnet gas prices have dropped considerably: by mid-2026, average gas prices ranged between 0.16 and 9 gwei.

Mitigation Strategies

Several techniques help users and applications manage congestion effectively. For a detailed guide on Bitcoin-specific strategies, see the fee bumping guide.

Fee Estimation

Accurate fee estimation is the first line of defense against overpaying or underpaying during congestion. Algorithms analyze current mempool conditions and historical confirmation data to recommend fee rates for different urgency levels. Bitcoin Core's estimatesmartfee RPC provides estimates targeting confirmation within a specified number of blocks.

Replace-By-Fee (RBF)

Replace-by-fee allows users to rebroadcast an unconfirmed transaction with a higher fee, effectively "unsticking" it from the mempool backlog. Since Bitcoin Core 28.0 adopted full RBF by default, any unconfirmed transaction can be replaced with a higher-fee version. This is particularly valuable when congestion spikes unexpectedly after a transaction was already broadcast.

Child-Pays-for-Parent (CPFP)

CPFP is an alternative fee-bumping technique where the recipient creates a new transaction spending the unconfirmed output, attaching a high enough fee to incentivize miners to include both the parent and child transactions together. This is useful when the original sender did not signal RBF.

Transaction Batching

Transaction batching combines multiple payments into a single transaction with multiple outputs. Instead of creating one transaction per recipient, exchanges and payment services can batch dozens of payments into one transaction, reducing the total block space consumed and the per-payment fee cost. Major exchanges save significant block space through batching during high-congestion periods.

Layer 2 Offloading

The most effective long-term solution to congestion is moving transactions off-chain entirely. Layer 2 protocols process transactions on a separate layer while inheriting the security of the base chain. On Bitcoin, the Lightning Network handles instant payments through payment channels, and Spark enables off-chain transfers without requiring channels at all. On Ethereum, rollups like Arbitrum and Optimism batch thousands of transactions into single on-chain proofs, dramatically reducing per-transaction costs.

Why It Matters

Network congestion is one of the primary user experience problems in cryptocurrency. When fees spike from $1 to $100 during congestion, small-value transactions become economically infeasible. A $10 payment that costs $50 in fees defeats the purpose of using the network. This is especially problematic for use cases like micropayments, remittances, and point-of-sale purchases where cost predictability is essential.

Congestion also creates equity issues: users who can afford to pay high fees get fast confirmations, while users with smaller transactions are priced out entirely. During the April 2024 fee spike, a standard Bitcoin transfer cost over $100, making the network unusable for everyday payments.

This is precisely why Layer 2 solutions exist. Spark processes payments off-chain with instant finality and predictable costs, regardless of how congested the Bitcoin base layer becomes. Users only interact with the base chain when entering or exiting the Layer 2, insulating routine transactions from fee volatility. For a comparison of how different Layer 2 approaches handle this, see the Bitcoin Layer 2 comparison.

Risks and Considerations

Fee Unpredictability

Congestion can spike without warning. A viral token launch or protocol exploit can fill the mempool in minutes, catching users off guard with transactions already broadcast at low fee rates. Without RBF enabled, those transactions may be stuck for hours or days until the mempool clears.

Dust Becomes Unspendable

During high-fee periods, small UTXO outputs (known as dust) become economically unspendable: the fee required to include them in a transaction exceeds their value. This effectively locks up funds until fees drop, and in extreme cases, the dust may never be worth spending.

Time-Sensitive Transactions at Risk

Protocols that rely on timely on-chain settlement are vulnerable during congestion. Lightning Network force-close transactions, justice transactions, and HTLC timeout claims all need to confirm within specific windows. If congestion delays them past their deadlines, funds can be lost. This risk underscores the importance of fee spike preparedness for any protocol with on-chain time constraints.

Centralization Pressure

Sustained high fees push users toward custodial services that can batch transactions and absorb fee costs, creating centralization pressure. If only large entities can afford on-chain transactions, individual self-custody becomes less practical, undermining a core value proposition of cryptocurrency.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.