Bitcoin you can see but not spend
Some UTXOs are included in a wallet's balance but are so small that sending them would cost more in fees than they hold. Such outputs are commonly called dust. On paper it is your bitcoin; economically, there is no reason to spend it.
This guide shows with a hypothetical calculation why small UTXOs become hard to spend and how the same UTXO's economics change with the fee rate. It covers nodes' dust threshold, the privacy risk of small amounts sent by strangers, and ways to manage small UTXOs.
What spending a UTXO costs
As the Bitcoin Developer Guide explains, Bitcoin transactions spend outputs of earlier transactions as inputs. Each input adds data such as a signature, and the fee is the transaction's size multiplied by the fee rate. The cost of spending a UTXO is therefore roughly fixed, regardless of how much it holds.
A common native SegWit (P2WPKH) input is about 68 vB. At 20 sat/vB, spending one such input costs about 1,360 sats. A UTXO worth less than 1,360 sats loses money to spend at that rate.
UTXO economics by fee rate
The table calculates, in a hypothetical example, what remains when spending UTXOs of 500, 2,000, and 10,000 sats at fee rates of 5, 20, and 50 sat/vB. Each input is assumed to be 68 vB.
| UTXO value | 5 sat/vB (cost 340) | 20 sat/vB (cost 1,360) | 50 sat/vB (cost 3,400) |
|---|---|---|---|
| 500 | +160 | −860 (loss) | −2,900 (loss) |
| 2,000 | +1,660 | +640 | −1,400 (loss) |
| 10,000 | +9,660 | +8,640 | +6,600 |
The same 2,000-sat UTXO is worth spending on a low-fee day and loses money on a high-fee day. Dust is not a fixed amount but a threshold that moves with the fee rate.
Nodes' dust threshold
Bitcoin Core's relay policy source defines a minimum fee rate for determining dust, and transactions creating outputs below the resulting threshold are treated as non-standard and not relayed by default nodes. A comment in the source notes that changing the dust limit changes which transactions are standard and should be done with care. The threshold depends on the output type and is commonly a few hundred sats.
This policy keeps the network from filling up with useless tiny outputs. As the table shows, though, outputs well above the policy threshold can still be uneconomical to spend when fees are high.
Unsolicited small deposits
Sometimes tiny amounts arrive at an address from an unknown source. Such deposits can be used to encourage users to later spend that UTXO together with others in one transaction, creating a link showing that several addresses belong to the same person. Bitcoin.org's privacy guidance also explains that spending inputs from several addresses together can link them.
It is often safer to leave small UTXOs of unknown origin unspent. Marking them as do-not-spend with a wallet's coin control feature stops the wallet from automatically mixing them with other inputs.
Not every unexpected deposit is hostile; some come from exchanges or services sending small test amounts. The safe default is the same either way: leave it alone until you know where it came from.
Managing small UTXOs
If you receive small payments often, small UTXOs pile up easily. Work through these steps.
- Review each UTXO's value and origin in your wallet's UTXO list or coin control view.
- Calculate the cost of spending one input at the current fee rate and identify UTXOs worth less.
- Mark small UTXOs of unknown origin as do-not-spend.
- If you hold many small UTXOs you received, consider consolidating them when fees are low.
- When consolidating, weigh the privacy effect of linking UTXOs from different sources.
Pros and cons of consolidating
Combining small UTXOs into one while fees are low lets you build smaller transactions with fewer inputs later when fees are high, cutting costs. It also rescues amounts, like the 2,000-sat UTXO in the table, that would become unspendable as fees rise.
A consolidation transaction, however, records on the public ledger that all those UTXOs belong to the same owner. Merging money received for different purposes can link transaction histories that had looked separate. You have to weigh cost against privacy yourself.
What this example leaves out
The amounts, input size, and fee rates here are hypothetical. Real input sizes depend on address type, and node policy thresholds can change with updates.
When managing UTXOs, check Bitcoin developer documentation and your wallet's current guidance with their dates. None of the figures here are a signal to buy or sell.