Bitcoin UTXO Consolidation Savings Calculator
Calculate how much you can save by consolidating Bitcoin UTXOs during low-fee periods. Compare costs by address type, fee rate, and UTXO count.
Why UTXO Consolidation Saves Money
Every unspent transaction output (UTXO) you hold adds cost to future transactions. When your wallet constructs a payment, each input it selects contributes 57 to 148 virtual bytes depending on the address type. During fee spikes, those extra bytes translate directly into higher fees. The April 2024 Runes launch pushed priority fee rates above 2,750 sat/vB, meaning a single P2WPKH input cost over 187,000 sats (roughly $125 at the time) just to include in a transaction.
UTXO consolidation merges multiple small UTXOs into a single larger one during low-fee periods, locking in cheap input costs before the next fee spike. The math is straightforward: consolidate 50 inputs at 2 sat/vB and you pay 6,883 sats total. Leave them unconsolidated and spend during a 50 sat/vB spike, and those same inputs cost 170,000+ sats. This guide breaks down the exact costs, savings, timing strategies, and trade-offs.
Consolidation Cost by UTXO Count
The following table shows the total fee for consolidating N native SegWit (P2WPKH) inputs into a single P2WPKH output at various fee rates. Transaction size is calculated as: 10.5 vB overhead + (N × 68 vB per input) + 31 vB output.
| UTXO Count | Tx Size (vB) | 1 sat/vB | 2 sat/vB | 5 sat/vB | 10 sat/vB | 50 sat/vB |
|---|---|---|---|---|---|---|
| 10 | 722 | 722 sats | 1,444 sats | 3,610 sats | 7,220 sats | 36,100 sats |
| 50 | 3,442 | 3,442 sats | 6,884 sats | 17,210 sats | 34,420 sats | 172,100 sats |
| 100 | 6,842 | 6,842 sats | 13,684 sats | 34,210 sats | 68,420 sats | 342,100 sats |
| 500 | 34,042 | 34,042 sats | 68,084 sats | 170,210 sats | 340,420 sats | 1,702,100 sats |
At 1 to 2 sat/vB, consolidating 100 UTXOs costs under 14,000 sats. The same 100 inputs would add over 340,000 sats in fees if spent individually during a 50 sat/vB congestion period. Use our consolidation calculator to model your specific UTXO set.
Per-Input Cost by Address Type
Not all UTXOs are equal. Legacy P2PKH inputs consume 148 vB each, while Taproot (P2TR) inputs require only 57.5 vB for a key-path spend. The address type of your existing UTXOs determines how much consolidation costs and how much you save.
| Address Type | Input Size (vB) | 1 sat/vB | 5 sat/vB | 20 sat/vB | 50 sat/vB | 200 sat/vB |
|---|---|---|---|---|---|---|
| P2PKH (legacy) | 148 | 148 sats | 740 sats | 2,960 sats | 7,400 sats | 29,600 sats |
| P2SH-P2WPKH (nested SegWit) | 91 | 91 sats | 455 sats | 1,820 sats | 4,550 sats | 18,200 sats |
| P2WPKH (native SegWit) | 68 | 68 sats | 340 sats | 1,360 sats | 3,400 sats | 13,600 sats |
| P2TR (Taproot key-path) | 57.5 | 58 sats | 288 sats | 1,150 sats | 2,875 sats | 11,500 sats |
Legacy P2PKH inputs are 2.6x more expensive than Taproot inputs at every fee level. If you still hold UTXOs on legacy addresses, consolidation serves double duty: you reduce your UTXO count and migrate to a cheaper address format. For a comparison of address types and their fee implications, see the address type fee savings tool.
Potential Savings: Consolidate Now, Spend Later
The core value proposition of consolidation: pay a small per-input fee now at low rates and avoid paying a much larger per-input fee later during congestion. The table below shows how much you save per P2WPKH input by consolidating at 2 sat/vB versus leaving them unconsolidated for a future spend at higher rates.
| Future Fee Rate | Cost Without Consolidation | Locked-In Cost (2 sat/vB) | Savings Per Input | 50 Inputs Saved | 100 Inputs Saved |
|---|---|---|---|---|---|
| 10 sat/vB | 680 sats | 136 sats | 544 sats | 27,200 sats | 54,400 sats |
| 20 sat/vB | 1,360 sats | 136 sats | 1,224 sats | 61,200 sats | 122,400 sats |
| 50 sat/vB | 3,400 sats | 136 sats | 3,264 sats | 163,200 sats | 326,400 sats |
| 100 sat/vB | 6,800 sats | 136 sats | 6,664 sats | 333,200 sats | 666,400 sats |
| 200 sat/vB | 13,600 sats | 136 sats | 13,464 sats | 673,200 sats | 1,346,400 sats |
Consolidating 100 P2WPKH inputs at 2 sat/vB costs 13,684 sats. If fees later spike to 50 sat/vB, you avoid 326,400 sats in input fees: a 24x return on the consolidation cost. Even at a moderate 20 sat/vB future rate, you save 122,400 sats against a 13,684-sat investment.
Dust Threshold Reference
A UTXO becomes dust when spending it costs more in fees than it contains. Bitcoin Core enforces a dust limit as a relay policy (not a consensus rule) using a default dust relay fee of 3 sat/vB. UTXOs below these thresholds are uneconomical to spend at any reasonable fee rate and should be evaluated carefully before including them in a consolidation batch.
| Output Type | Dust Threshold | Calculation |
|---|---|---|
| P2PKH | 546 sats | 3 × (34 + 148) = 546 |
| P2SH | 540 sats | 3 × (32 + 148) = 540 |
| P2WPKH | 294 sats | 3 × (31 + 67) = 294 |
| P2WSH | 330 sats | 3 × (43 + 67) = 330 |
| P2TR | 330 sats | 3 × (43 + 67) = 330 |
At fee rates above 1 sat/vB, the effective "economic dust threshold" is higher than the relay policy minimum. For example, spending a P2WPKH input at 10 sat/vB costs 680 sats, so any UTXO under 680 sats is uneconomical at that rate even though it clears the 294-sat relay threshold. Use our dust calculator to determine which UTXOs in your wallet are worth consolidating.
When to Consolidate: Timing Strategies
Fee rates on Bitcoin follow predictable patterns driven by network activity, time zones, and market events. Understanding these patterns helps you consolidate at the lowest possible cost.
Weekly patterns:
- Weekends consistently see lower fees than weekdays, with Sunday typically the cheapest day
- The quietest window is 03:00 to 09:00 UTC, between US close and Asian market opens
- Monday mornings (UTC) often see fee spikes as exchanges batch withdrawals
Fee environment signals:
- Monitor the mempool for sustained periods at 1 to 2 sat/vB (these are ideal consolidation windows)
- Extended low-fee periods like mid-2025 through 2026, when the median fee rate sat at 1 to 2 sat/vB for months, are prime consolidation opportunities
- Set fee rate alerts using mempool monitoring tools and consolidate when your target rate is available
Enable replace-by-fee (RBF) on your consolidation transaction. If the mempool clears further after you broadcast, your transaction confirms at the rate you set. If fees spike, you can bump the fee to avoid the transaction sitting unconfirmed. For deeper analysis of fee cycles, see our fee market dynamics research.
Privacy Trade-Offs: Address Clustering Risk
Consolidation comes with a significant privacy cost. Address clustering analysis relies on the common-input-ownership heuristic: if multiple inputs appear in the same transaction, chain analysis firms assume they belong to the same entity. A consolidation transaction with many inputs and one output is the clearest possible signal that all those addresses share a single owner.
This linking is permanent and public on the blockchain. Once addresses are clustered, every future transaction from any of those addresses is associated with the same entity. Research has shown that applying the common-input heuristic alongside change-output detection can collapse hundreds of millions of Bitcoin addresses into tens of millions of entity clusters.
Privacy-preserving consolidation strategies:
- Never mix UTXOs from different privacy contexts (exchange withdrawals, peer-to-peer, mining) in the same consolidation transaction
- Use coin control features in your wallet to manually select which UTXOs to consolidate together
- Consolidate to a fresh address that has no prior transaction history
- Consider CoinJoin or PayJoin transactions that break the common-input assumption by mixing inputs from multiple parties
- Accept that consolidation reduces privacy and decide whether the fee savings justify the trade-off for your threat model
For a detailed analysis of on-chain privacy techniques, see our transaction graph privacy defenses research.
When Consolidation Is Not Worth It
Consolidation is not always the right strategy. In several scenarios, leaving UTXOs fragmented is the better choice:
- Privacy-sensitive wallets where linking addresses would compromise your security model
- UTXOs below the economic dust threshold at your target consolidation fee rate (spending more on fees than the UTXO contains)
- Already-low UTXO counts (under 5 to 10 UTXOs), where the savings from consolidation are marginal
- Wallets used for CoinJoin mixing, where UTXOs are intentionally kept separate at standard denominations
- Fee rates above 10 sat/vB, where the consolidation cost itself starts to erode the potential savings
The break-even calculation is simple: if the cost to consolidate N inputs now (at current rate) exceeds the savings you would realize by having one fewer input later (at a realistic future rate), skip consolidation. Use the savings table above to estimate your break-even point.
How Spark Eliminates UTXO Management
The entire concept of UTXO consolidation exists because Bitcoin's UTXO model requires wallets to track and manage individual outputs. Every received payment creates a new UTXO, and every spend must reference specific UTXOs as inputs, paying per-input fees. Over time, regular Bitcoin users accumulate hundreds of UTXOs that fragment their balance and inflate future transaction costs.
Spark uses a fundamentally different approach. Instead of managing individual UTXOs on the base layer, Spark operates as a Bitcoin layer 2 where balances are tracked without UTXO fragmentation. Users send and receive bitcoin and stablecoins like USDB with instant settlement and near-zero fees, regardless of how many payments they have received. There are no inputs to consolidate, no dust thresholds to worry about, and no fee-rate timing strategies required.
For users who need on-chain Bitcoin for specific use cases (multisig custody, cold storage, large settlements), UTXO consolidation remains an essential practice. For everyday payments and dollar-denominated transfers, Spark removes the problem entirely. See our introduction to Spark for a full technical overview.
Frequently Asked Questions
What is UTXO consolidation in Bitcoin?
UTXO consolidation is the practice of combining multiple unspent transaction outputs into a single, larger UTXO by sending them to yourself in one transaction. This reduces the number of inputs your wallet needs to include in future transactions, lowering fees when you eventually spend. The optimal strategy is to consolidate during low-fee periods (1 to 2 sat/vB) so the consolidation itself is cheap.
How much does it cost to consolidate 100 Bitcoin UTXOs?
For 100 native SegWit (P2WPKH) UTXOs consolidated into one output, the transaction size is approximately 6,842 vB. At 1 sat/vB, this costs 6,842 sats. At 2 sat/vB, it costs 13,684 sats. At 5 sat/vB, it costs 34,210 sats. Legacy P2PKH UTXOs are more expensive: the same 100 inputs would produce a transaction of roughly 14,842 vB, costing 14,842 sats at 1 sat/vB.
When is the best time to consolidate Bitcoin UTXOs?
The best time is during sustained low-fee periods when the mempool is near-empty and the next-block fee rate is 1 to 2 sat/vB. Historically, weekends (especially Sundays) and the 03:00 to 09:00 UTC window see the lowest activity. Extended low-fee environments, like the period from mid-2025 through 2026 when median fees held at 1 to 2 sat/vB, are ideal windows to consolidate large UTXO sets.
Does UTXO consolidation affect privacy?
Yes. Consolidation directly harms privacy by linking all input addresses in the same transaction. Chain analysis firms use the common-input-ownership heuristic to assume that all inputs in a transaction belong to the same entity. This association is permanently recorded on the blockchain. To mitigate this, never consolidate UTXOs from different privacy contexts, use coin control to select inputs manually, and consider whether the fee savings justify the privacy cost for your specific threat model.
What is the Bitcoin dust threshold?
The dust threshold is the minimum UTXO value that Bitcoin Core nodes will relay. It is calculated as 3 sat/vB multiplied by the sum of the output size and the cost to spend it. For P2WPKH outputs, the threshold is 294 sats. For P2TR and P2WSH, it is 330 sats. For legacy P2PKH, it is 546 sats. UTXOs below these values are considered dust and are rejected by default relay policy.
Should I consolidate dust UTXOs?
It depends on the fee rate. A dust UTXO is only worth consolidating if its value exceeds the fee to spend it. For example, a 500-sat P2WPKH UTXO costs 68 sats to spend at 1 sat/vB (net gain of 432 sats) but costs 3,400 sats to spend at 50 sat/vB (net loss of 2,900 sats). Use the dust calculator to identify which UTXOs in your wallet are economically viable to consolidate at current fee rates.
How does Taproot reduce consolidation costs compared to SegWit?
Taproot (P2TR) key-path spend inputs are 57.5 vB, compared to 68 vB for native SegWit (P2WPKH). That is a 15.4% reduction per input. Over 100 inputs, this saves 1,050 vB, which at 10 sat/vB equals 10,500 sats. Taproot also produces slightly larger outputs (43 vB vs 31 vB), but since consolidation produces only one output, the per-input savings far outweigh the output difference. For UTXO management strategies including address-type migration, see our research guide.
Can I consolidate UTXOs from different address types?
Yes. A single Bitcoin transaction can include inputs from different address types (P2PKH, P2WPKH, P2TR, etc.) and send to any output type. This is a common pattern when migrating from legacy to SegWit or Taproot addresses. Each input still costs its own per-type vBytes: a transaction mixing 5 P2PKH inputs (148 vB each) with 5 P2WPKH inputs (68 vB each) would use 740 + 340 = 1,080 vB for the inputs alone. When consolidating mixed types, use your wallet's coin selection features to verify the total transaction size before broadcasting.
This tool is for informational purposes only and does not constitute financial advice. Transaction sizes are based on standard single-signature key-path spends and may differ for multisig, script-path, or non-standard spending conditions. Fee rates fluctuate continuously. Always verify current mempool conditions before broadcasting consolidation transactions.
Build with Spark
Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.
Read the docs →
