What Is Dust in Bitcoin? The Dust Limit and Dusting Attacks

Anyone who has held bitcoin for a while ends up with a few tiny leftover amounts, some sent on purpose. Understanding what dust is, where the dust limit comes from, and how a dusting attack works turns those confusing specks into something you can reason about instead of worry over.

What is dust in Bitcoin?

Dust in Bitcoin is an unspent transaction output (UTXO) whose value is smaller than the fee it would take to spend it. Because Bitcoin balances are made of discrete unspent transaction outputs, not a single running total, every coin you hold is a separate chunk that costs a bit of fee to include as an input. When a chunk is worth less than that cost, spending it is a net loss: you would pay, say, 700 satoshis in fees to move a 500 satoshi output. That economically unspendable output is dust. It still belongs to you and it is still visible on the chain, it just cannot be moved without you subsidizing the fee from other coins.

What is the Bitcoin dust limit?

The dust limit is the threshold below which a Bitcoin node treats an output as uneconomical and refuses to relay a transaction that creates it. In Bitcoin Core the limit is not a fixed number of satoshis but a calculation: an output is dust if moving it would cost more than one third of its value in fees, evaluated at a reference fee rate. In practice that works out to about 546 satoshis for a legacy or P2SH output and around 294 satoshis for a native SegWit output, because SegWit inputs are cheaper to spend. Wallets use these figures to avoid creating outputs nobody could ever spend at a profit.

These numbers assume a low reference fee rate. When network fees rise, the amount that counts as unspendable in practice rises with them, so an output that was worth moving during a quiet week can become dust during a busy one. To see the exact set of outputs behind any address, including the tiny ones, you can query Bitcoin UTXO data directly rather than infer it from a wallet display.

What is a dusting attack?

A dusting attack is when someone sends tiny amounts of bitcoin to many addresses, then watches the chain to see when those specks get combined with other coins in a single transaction. Bitcoin is pseudonymous, not anonymous, so when a wallet spends the dust alongside your other UTXOs, it reveals that all those inputs share one owner. That linkage is what the attacker is after: it clusters your addresses together and can chip away at the privacy separation you thought you had between them. The dust itself is harmless money; the risk is entirely in what spending it exposes.

This is also why address attribution is a legitimate analytics discipline rather than magic. Clustering heuristics like common-input-ownership are exactly what compliance and research teams rely on to attach Bitcoin address labels to exchanges, services and known entities. The same on-chain behavior that a dusting attacker exploits is what lets an analyst say, informationally, that a set of addresses appears to share control.

How do I get rid of Bitcoin dust?

The safest way to handle dust is often to do nothing, because leaving it unspent means it never links your addresses. If you do want to clear it, you have a few practical options. Use a wallet with coin control so you can choose exactly which UTXOs to spend and keep suspicious dust out of unrelated transactions. Consolidate your own small outputs during a low-fee period, when combining many tiny inputs into one is cheap. Or mark specific dust outputs as do-not-spend in wallets that support freezing coins, so they are excluded from automatic coin selection. Never spend attacker-sent dust together with coins whose privacy you care about.

Is Bitcoin dust worth anything?

Bitcoin dust is worth its face value in satoshis, but that value is usually less than the fee required to spend it, which is what makes it economically stranded rather than truly worthless. A 400 satoshi output is real bitcoin, and if the price rises far enough or fees fall far enough, it could one day be worth moving. For now, treat dust as a rounding error you keep an eye on, not a balance you can reliably access. If you receive crypto as part of your work, remember that even small amounts count as income at their fair value when received, which is why creators and sellers who take crypto often track every payout for taxes rather than ignore the small ones.

Does spending dust hurt my privacy?

Yes, spending attacker-sent dust can hurt your privacy, because it lets an observer link the dusted address to the other addresses whose coins you spend alongside it. That is the entire mechanism of a dusting attack. The moment two inputs appear in the same transaction, the common-input-ownership heuristic assumes they share an owner, so a carefully separated set of addresses collapses into one cluster. Using coin control to isolate dust, or simply never spending it, keeps that linkage from ever being created and preserves the separation you set up.

Read the chain yourself

Dust is a good reminder that a Bitcoin balance is really a pile of individual outputs, each with its own size and history. When you can see those outputs directly, coin control, fee planning and privacy all get easier to reason about. BitcoinDatabase indexes every output on the chain, so you can look up the exact UTXOs behind any address, spot dust, and trace where it came from over a clean API, SQL or dashboards. Try it from the console above, and this is informational on-chain data only, not financial or investment advice.