UTXO Fragmentation

Overview

A fragmented wallet must select many inputs to fund a large outgoing transaction. Each input adds bytes or weight, which raises the network fee and can approach protocol or policy size limits. During congestion, a technically sufficient balance can become operationally difficult to move.

Fragmentation differs from dust because individual outputs may still be economically spendable. The problem is their quantity and distribution relative to future payment sizes. A business receiving hundreds of customer payments can experience fragmentation even when every deposit is meaningful.

Wallets manage fragmentation through coin selection, batching, change-size strategy, and planned consolidation. Creating several medium-sized treasury outputs can support future payouts more efficiently than one large output or thousands of small ones.

Privacy considerations remain important. Consolidating many deposits can link customer-facing addresses. Separating wallets or UTXO groups by purpose can preserve accounting and privacy boundaries at the cost of lower fee efficiency.

Operational monitoring should track UTXO count, size distribution, estimated consolidation cost, and the number of inputs required for typical payouts. Fragmentation is best addressed before an urgent transaction is needed. It is a liquidity-structure problem, not a shortage of total asset value.

Fragmentation can also cause transaction-construction failures when the wallet or hardware signer limits the number of inputs it can process. Treasury teams should simulate typical and worst-case payouts before periods of expected demand. Maintaining a distribution of output sizes aligned with normal withdrawals can reduce both urgent consolidation and excessive change creation. Regular reporting makes the problem visible before it becomes urgent.