How Bitcoin Fees Work in 2026 — And How to Pay Less Reading the Mempool

Bitcoin doesn't have flat fees. Every transaction is an auction bid for a limited resource — block space — and the auction clears every ten minutes when the next block gets mined. Pay too little and your transaction sits in the mempool for hours or days. Pay too much and you're tipping miners for no reason. Knowing how the auction actually works is the difference between a $0.30 transaction and a $30 one for the same send.

This guide walks the mempool, fee math, and the practical workflow for paying the right amount. Same destination, much less wasted satoshi.

Block space, the limit that matters

Every ten minutes, one Bitcoin block gets mined. The block has a hard size cap — historically 1MB, then changed by SegWit in 2017 to a "weight" limit equivalent to roughly 4MB of total data using witness discount. Roughly 2,000 to 3,500 transactions fit per block depending on transaction complexity. Demand for that block space varies wildly: 5 sats per virtual byte during quiet weekends, 200+ sats per vB during congestion peaks.

The miner's job is to pick which transactions go into the next block. The selection criterion is fee per byte — they take the highest-paying transactions first because that maximizes their revenue. Your transaction's competition is every other unconfirmed transaction sitting in the mempool.

Fee rates, in sats per virtual byte

Bitcoin fees aren't quoted in dollars or even in BTC. They're quoted in sats per virtual byte (sats/vB). Your transaction's total fee is its size in vBytes multiplied by the rate.

Typical transaction sizes:

• Simple SegWit send (1 input, 2 outputs): ~140 vB
• Taproot send (1 input, 2 outputs): ~110 vB
• Multisig 2-of-3 send: ~250-400 vB
• UTXO consolidation (10 inputs, 1 output): ~600 vB

At 5 sats/vB during quiet times, a 140-vB transaction costs 700 sats — about $0.50 at $80,000/BTC. At 100 sats/vB during congestion, the same transaction costs 14,000 sats — about $11. The transaction is identical; the auction price changed.

Reading the mempool

Mempool.space is the standard public mempool visualizer. The fee histogram shows current fee rates and how full the mempool is at each rate. Three rates to know:

• "Next block" rate: what miners are taking right now to get into the very next block.
• "~30 min" rate: what gets you into a block within roughly 3 blocks.
• "~1 hour" rate: what gets you into a block within roughly 6 blocks.

For most non-urgent sends, the 1-hour rate is usually 30-50% cheaper than next-block and the wait is fine. For genuine urgency, pay next-block. Don't pay above next-block; you're just tipping the miner.

When fees are low

Empirically, fees are lowest:

• Weekends, especially Sunday morning UTC.
• US/EU overnight hours.
• Outside of price-spike news cycles.
• Outside of Inscriptions/Ordinals minting waves (these load the mempool with non-payment transactions willing to pay high rates).

Use these windows for non-urgent sends and especially for UTXO consolidation. A consolidation that costs $50 in fees during congestion costs $3 during a calm Sunday morning.

RBF and CPFP: how to fix a stuck transaction

You sent a transaction with a fee that's too low and it's been sitting in the mempool for six hours. Two ways out:

RBF (Replace-By-Fee, BIP-125): if your wallet flagged the transaction as RBF-eligible at send time (most do by default in 2026), you can broadcast a new version with a higher fee that replaces the original. Bitcoin Core, Sparrow, Trezor Suite, BlueWallet, and most modern wallets support RBF natively.

CPFP (Child-Pays-For-Parent): if you can't or don't want to RBF — for example, the recipient already saw the transaction — you can spend the unconfirmed output in a new transaction with a fee high enough to incentivize miners to pull both into a block. Works when you control either the change output or the receiving address.

Sparrow Wallet exposes both clearly. Most mobile wallets support RBF but hide CPFP. Trezor Suite, Ledger Live, and BitBoxApp all expose RBF in their send confirmation flow.

Address types and fee math

Modern Bitcoin addresses come in four flavors:

• Legacy (`1...`): oldest, largest, most expensive to spend.
• P2SH (`3...`): wraps SegWit in a legacy-compatible package, smaller than legacy.
• Native SegWit (`bc1q...`): SegWit-only, ~25-40% smaller than legacy.
• Taproot (`bc1p...`): the 2021 SegWit v1 upgrade, slightly smaller than `bc1q`, with privacy and scripting upgrades.

Spending from native SegWit or Taproot addresses is meaningfully cheaper than spending from legacy ones. If you have legacy UTXOs, consolidate them into Taproot during low-fee periods. Receive at Taproot addresses going forward where your wallet supports it.

Batching

One transaction with three outputs is much cheaper than three transactions with one output each. Exchanges batch withdrawals to dozens of users in single transactions. Individual users can do the same logic when sending to multiple recipients — just send all of them in one transaction with multiple outputs.

Sparrow Wallet exposes "send to multiple recipients" cleanly. Most other wallets don't, which means you're sending one transaction at a time and paying for redundant overhead.

Wallets that save you fees

Wallets with strong fee UX:

• Sparrow Wallet: coin control, custom fee rates, RBF, CPFP, multi-recipient, the works. Desktop only.
• Trezor Suite: RBF supported, fee selection clear, integrates with Sparrow.
• BlueWallet: mobile, supports RBF, fee selection.
• Phoenix (Lightning): sidesteps the fee question entirely by routing payments through Lightning channels.

Wallets to avoid for fee-sensitive use: anything that hides the fee selection behind a "Slow / Medium / Fast" abstraction without showing the underlying sats/vB. You're paying real money; you should see what you're paying.

Reference hardware wallet for power-user fee management: Trezor Safe 5 at $129 paired with Sparrow on desktop. Or any of the wallets in our hardware wallets pillar.

Related on BTCLinks

Frequently asked questions

How are Bitcoin fees calculated?

Bitcoin fees are paid per virtual byte (vB) of transaction data, not per dollar amount. A simple transaction is about 140 vB; a complex multi-input one might be 400 vB. Your wallet picks a fee rate (sats/vB) based on current mempool congestion. Total fee = transaction size × fee rate.

What is the mempool?

The mempool is the pool of unconfirmed Bitcoin transactions waiting to be included in a block. Each Bitcoin node maintains its own mempool. Miners select transactions from their mempool to include in the next block, generally choosing the highest fee-per-byte transactions first.

What is RBF (Replace-By-Fee)?

RBF lets you replace an unconfirmed Bitcoin transaction with a new version that pays a higher fee. Useful when your original transaction is stuck. The wallet must support it (most modern ones do) and the original transaction must be flagged RBF-enabled when you sent it.

How do I pay less in Bitcoin fees?

Send during low-mempool times (weekends and US/EU overnight hours typically have the lowest fees). Use a wallet that lets you set custom fee rates. Consolidate UTXOs during low-fee periods. Use SegWit/Taproot addresses (smaller transaction sizes). Batch outputs when sending to multiple recipients.

Sources

• BIP-125: Opt-in Full Replace-by-Fee Signaling — the standard for RBF.
• BIP-141: Segregated Witness — the 2017 upgrade that introduced witness discount and changed fee math.
• BIP-341: Taproot — the 2021 upgrade introducing `bc1p` addresses.
• mempool.space — the standard public mempool visualizer (open source, self-hostable).

Some links are affiliate links. As an Amazon Associate we earn from qualifying purchases. Not financial advice.