Consolidation Transaction
A transaction combining multiple small UTXOs into a single output, typically done during low-fee periods.
A consolidation transaction takes many small UTXOs and combines them into one larger output. It's the cleanup pass for a wallet that's accumulated lots of small inputs over time.
The motivation is fee efficiency. Every input in a transaction takes up bytes (roughly 68-148 depending on script type), and bigger transactions cost more in fees. If you have 50 small UTXOs and want to spend them later, every future transaction that touches multiple of them pays for all those input bytes. Consolidating during a low-fee period means paying once for the bytes now, saving on every spend after.
The practical recipe:
- Wait for a low-fee window. Watch the mempool and consolidate when next-block fees drop to 1-3 sat/vB. Idle weekends and post-rally calm periods are common windows.
- Pick the UTXOs deliberately. Consolidating UTXOs from different sources publicly links them. If you've been carefully keeping certain addresses separate for privacy reasons, do not combine them in one consolidation transaction.
- Send to a fresh address in your own wallet. The output is a single new UTXO controlled by you.
The privacy tradeoff is real. Consolidation tells the public chain: "these UTXOs all share an owner." If they came from KYC sources or distinct identity contexts, you've just linked them. The right move when privacy matters is to consolidate UTXOs that are already publicly linked (came from the same source, were already used together) rather than mixing isolated ones.
Exchanges and merchants do this routinely as ordinary operations. Individual users typically consolidate every few months if at all. See Dust for the small-UTXO problem this addresses.
Key takeaways
- Combines small UTXOs into fewer, larger outputs
- Reduces future transaction fees and wallet clutter
- Can compromise privacy if inputs come from distinct addresses