Crypto Fee Watch/2026-09-13
transaction troubleshootingFigures current as of

What Congestion Actually Looks Like

The observable signals of a busy network, where to see them, and what each one means for a transaction you are about to send.

Tom Beecher · 2 min read

Congestion is not a state the network announces. It is a set of observable conditions, and checking them takes about thirty seconds.

The signals

Base fee rising across consecutive blocks. The base fee increases when blocks are more than half full. Several consecutive increases means demand exceeds the target.

Blocks at or near the maximum size. Elastic capacity means blocks can exceed the target during spikes. Consistently full blocks mean the elasticity is being used.

Mempool depth growing. More transactions waiting than recent blocks can clear.

The fee distribution in the pending set widening. When the gap between the lowest and highest fees among pending transactions grows, competition is increasing.

Confirmation times lengthening for transactions at a given fee level.

Where to see them

Block explorers show the base fee and block fullness directly. Several sites visualise mempool state, including how many transactions are waiting at each fee level and what the next few blocks are likely to contain.

That last view is the most useful single display available, because it shows the actual queue rather than a prediction derived from it.

The categories of congestion

Cyclical. The daily and weekly pattern. Predictable, moderate, and entirely avoidable by timing.

Event-driven. A large mint, an airdrop claim, a liquidation cascade. Sharp, short, and far above anything the cycles produce.

Sustained. A period of elevated activity lasting days. Less common and it changes what is economic to do on-chain at all.

What to do in each

Cyclical: wait for the weekend or the early morning if the operation is not urgent.

Event-driven: wait. These resolve within hours and transacting during one can cost several times the normal amount.

Sustained: move the activity to a rollup, or accept that mainnet operations are expensive for the period.

The stuck transaction question

During congestion, transactions submitted at pre-congestion fee levels wait. That is not a malfunction.

The options are to wait, since base fees fall when demand subsides, or to replace the transaction with a higher fee using the same nonce.

Waiting costs nothing and works more often than people expect. Replacing costs the new fee.

The preventive habit

Check the base fee before submitting anything discretionary. If it is elevated relative to recent days, and the operation can wait, wait.

For withdrawals from a venue, the network fee is handled by the platform, and platforms that display it separately, such as venues that quote the network fee separately, let you see the current cost and defer if it is high.

The habit takes ten seconds and is the single most effective fee management practice available.

On the numbers

Fees move with network demand. Any figure here reflects the date shown above and should be re-checked before you act on it. Where a measurement was taken by hand, the article says so.

congestionmempoolmonitoring

Related reports