What you pay for, how fee rates work and when waiting or batching can reduce cost.
Estimate block-space demand and transaction size instead of guessing from the amount sent.
- Fees follow transaction weight and demand, not payment value.
- Estimates are probabilistic.
- Batching and thoughtful UTXO management can lower long-run costs.
Buying scarce block space
A transaction fee is the difference between input and output value. Wallets express competitiveness as sats per virtual byte because miners generally optimize revenue against limited block weight. <strong>Mempools are local.</strong> Each node maintains its own view of valid unconfirmed transactions. Fee estimators infer likely inclusion from recent blocks and mempool conditions; they cannot guarantee an exact confirmation time.
<strong>Use available tools.</strong> Replace-by-fee can rebroadcast an enabled transaction with a higher fee. Child-pays-for-parent may incentivize confirmation of a transaction chain. Batching multiple payments and consolidating at quiet times can reduce future footprint.
Compare two transactions with the same payment
Wallet A pays 100,000 sats using one input and creates a recipient output plus change. Wallet B pays the same amount but must combine ten small inputs. Wallet B consumes more virtual bytes, so at the same 5 sat/vB rate it pays a larger absolute fee. The amount transferred is identical; the data footprint is not.
This is why many small withdrawals can become expensive to spend later. Before sending, inspect the estimated virtual size, current mempool bands, and urgency. A low-priority payment can use a lower rate if replacement is available and delay is acceptable. Batching several recipients may reduce repeated overhead.
Consolidating outputs during quiet conditions can help future spending, but it also links those outputs on the public ledger, so fee efficiency and privacy should be considered together.
Why the market works the way it does
Each block has room for about 4 million weight units, and blocks arrive roughly every ten minutes regardless of demand. When more transactions want in than fit, miners take the highest fee rates first and the rest wait.
The result is an auction that repeats every block: in quiet weeks a couple of satoshis per virtual byte clears in the next block, and in a rush - a price move, an exchange outage, a new token protocol writing data to the chain - the same position costs hundreds.
The historical fee explorer on this site shows those episodes and how quickly each one subsided.
Calculating what you will pay
Fee equals virtual size times fee rate. A typical single-input, two-output native SegWit payment is about 140 virtual bytes; at 10 sat/vB that is 1,400 sats, at 100 sat/vB it is 14,000. A legacy transaction with the same shape is about 225 vB. A consolidation spending twenty small inputs is well over 1,000 vB and should be done when rates are low.
The amount sent does not enter into it: moving one bitcoin and moving one dollar's worth from the same inputs cost the same. The UTXO planner on this site gives the size for any input and output mix.
Reducing fees without waiting forever
Use a native SegWit or Taproot wallet, whose inputs are the smallest. Batch several payments into one transaction with many outputs rather than several transactions. Consolidate small inputs during a quiet weekend so a later urgent payment needs only one. Set a low rate with replace-by-fee enabled and raise it only if the wait becomes a problem. Use Lightning for small, frequent payments.
And read the mempool before sending: a backlog that has been growing for hours will not clear at yesterday's rate, while one that is draining will.
Estimate from bytes and urgency
Start with the transaction's virtual size, then choose a fee rate from current mempool conditions and your time preference. The bitcoin amount being sent does not determine the miner fee.
Questions about choosing a fee
Why do Bitcoin fees change so much?
Block space is limited to about 4 million weight units per block, and demand varies by hour and by event. When more transactions wait than fit, users bid higher rates for the next block; when demand is low, a few sats per virtual byte clears quickly.
Is the fee based on how much I send?
No. It is based on the transaction's size in virtual bytes, which depends on the number and type of inputs and outputs. Sending one bitcoin and sending 0.001 bitcoin from the same inputs cost the same; consolidating many small inputs costs more.
What are RBF and CPFP?
Two ways to speed up a stuck transaction. Replace-by-fee lets the sender rebroadcast it with a higher fee; child-pays-for-parent lets the recipient spend the unconfirmed output with a high enough fee that miners take both together.
Sources and further reading
Primary documents this guide draws on. Links open the original publisher.
- Transaction fees Bitcoin Wiki
- BIP 141: Segregated Witness Bitcoin Improvement Proposals
- BIP 125: Opt-in full replace-by-fee signaling Bitcoin Improvement Proposals
- Developer guide: transactions developer.bitcoin.org