Why sending the same BTC amount can cost very different fees
The amount on a wallet’s balance screen is not enough to estimate its next transaction fee. Think of a hypothetical balance of 0.1 BTC: one wallet might spend a single suitable output, while another might need to spend twenty smaller outputs. A calculator that asks only “how much BTC?” misses that structural difference. Our anatomy visual holds the fee rate and output count constant so you can isolate the effect of input count and script type.
A worked comparison you can reproduce
Under this calculator’s native-SegWit upper-bound template, one input and two outputs occupy 141 virtual bytes. At an illustrative 3 sat/vB the estimated fee is 423 sats. Ten inputs with the same two-output template occupy 755 vB, giving 2,265 sats at the same rate. The larger fee does not require a larger BTC payment. The input count changed; the rate did not. At 30 sat/vB those same templates produce 4,230 and 22,650 sats respectively.
Those figures describe our specified templates, not a promise about an unknown wallet. We include transaction overhead, signature assumptions and the SegWit marker/flag. Rounding applies to virtual size and the final fee. Changing script types can change both the inputs and outputs, so “Taproot” is not automatically a universal lowest-cost answer for every count and spend path.
Keep price, size and urgency separate
A transaction’s vB estimate describes its construction. A sat/vB recommendation describes a provider’s current view of fee conditions. A BTC/USD quote converts units into an indicative dollar value. Multiplying them is mathematically straightforward, but the three inputs have different uncertainties. A large USD price move can change a dollar-denominated fee estimate even when the transaction size and sat/vB rate are unchanged.
Why this tool does not recommend consolidation
The slider can show that many inputs produce a larger transaction. That is an explanation, not an instruction to combine your coins. Consolidation has its own immediate fee, potential privacy consequences and wallet-specific trade-offs. We do not know your UTXOs, future spending needs or wallet’s coin-selection policy, and the tool never connects to your wallet. Use its output to understand a specified example rather than letting an animated bar make a financial decision for you.
Read the estimate’s timestamp
A “one-hour” recommendation is a target horizon in the source’s estimation, not a reservation in an upcoming block. If the source becomes delayed, that label is kept visibly separate from the observation time. Historical comparisons also need real coverage: a newly launched collector cannot honestly provide thirty days of measured history on its first evening.
Technical references: BIP 141 for weight and virtual size, Bitcoin transaction inputs and outputs, and mempool.space fee estimates. Supported templates and exclusions are listed above so the examples can be checked.