When Bitcoin traffic gets heavy, a full block does not stop the network; it turns the next available space into a live auction where urgency has a price.
Key Takeaways
Bitcoin blocks cap at 4 million weight units, forcing lower-fee payments to wait. Bitcoin Core 31.0 can evict weak packages when a node’s 300 MB mempool fills. Bitcoin users have 3 fee-bump paths, RBF, CPFP, and mining accelerators when congestion persists.Miners do not normally choose transactions by age. They build block templates around fees, transaction weight, and dependencies between payments. The practical unit users see is satoshis per virtual byte, or sat/vB. A higher rate offers miners more revenue for the same scarce block space, so the strongest fee packages tend to move first.
That means a payment sent first can be confirmed after one sent minutes later. A high-fee transaction may spread broadly across the network and land in miners’ next templates. A low-fee transaction can remain below the cutoff, even after several blocks pass. Confirmation estimates help, but they are not promises because new transactions arrive continuously and blocks themselves appear at irregular intervals.
Congestion Reaches the WalletFor an ordinary user, the first consequence is delay. A wallet may say a payment is pending for hours while newer transactions confirm. For a trader, exchange or treasury desk, that delay can postpone an exchange deposit, slow collateral movement, interrupt an arbitrage transfer or leave funds unavailable during a fast market.
Because fees are tied primarily to transaction weight rather than the value transferred, a $50 payment and a $5 million transfer can compete on similar terms when their transaction structures are comparable. The more time-sensitive the transfer, the more expensive underpaying can become.
