Separate folders, receipts and a face-down phone representing the information boundaries around a payment, editorial illustration
Privacy / GUIDE

Your balance is a collection of stories

Learn what UTXOs reveal, and make deliberate choices before you spend.

Start reading
4 min readEnglish
READING MODE

Look beneath the balance

A wallet’s balance combines the amounts in its unspent transaction outputs, usually shortened to UTXOs. Each output comes from a previous transaction and can later be spent as an input. The interface may show one number, but the underlying pieces can have different histories and different privacy implications.

Imagine receiving one payment from a customer and another from a friend. Combining those outputs in a later transaction can create evidence that they were controlled together. That observation is not absolute proof in every transaction design, but it is a useful reason to understand what your wallet selects.

Watch UTXOs and coin control, explained in 2 minutes. Captions available.
YOUR COINSWHAT IT CREATES Coin A20,000 satsCoin B15,000 satsCoin C8,000 sats, not used Transaction35,000 sats in Payment30,000 satsChange to you4,400 satsFee to miners600 sats
Bitcoin has no account balance. A payment spends whole coins and creates new ones: the payment, your change, and the fee that is left over.

Label before you forget

Private labels can help you remember why an output exists. Use descriptions that make sense to you, such as a project name or a spending purpose, rather than relying on memory months later. Keep label backups protected: transaction metadata can be sensitive even when it contains no signing keys.

For a learning exercise, draw three fictional incoming payments and a purchase on paper. Decide which incoming payment should fund the purchase and where the remaining value goes. This small exercise makes the change output easier to recognize when you inspect a real wallet’s transaction preview.

Use coin control deliberately

Coin control lets you choose which outputs fund a payment. Sparrow’s official FAQ describes selecting outputs in its UTXOs view and using Send Selected. You can inspect the proposed transaction before signing; there is no need to create a real transfer merely to learn the interface.

Check the recipient, the selected inputs, the change destination and the fee. Spending an output consumes it in full; the transaction can return excess value as change. More inputs generally make a transaction larger, so a choice that seems tidy can affect both privacy and cost. Do not consolidate everything simply because fewer rows look cleaner.

Privacy is a routine, not a switch

Use fresh receiving addresses where your wallet supports them, avoid publishing transaction details unnecessarily, and consider which server learns your wallet queries. Running your own node can reduce reliance on a third-party server, but it does not erase the public transaction graph or remove the need to manage network privacy.

Coin control does not make bitcoin anonymous or undo earlier disclosures. Draw a fictional payment on paper, identify what each participant and the wallet server could learn, and choose one habit to improve. Repeat the exercise when your wallet or spending pattern changes.

Before changing a real wallet, explain your intended improvement in one sentence. If you cannot identify which disclosure it reduces, pause and learn more. More transactions and more tools do not automatically produce better privacy.

  • Use labels you can understand later.
  • Inspect inputs and change before signing.
  • Avoid combining unrelated histories without considering why.
  • Treat public transaction and wallet metadata as lasting disclosures.

Small outputs, fees and consolidation

Fees depend on transaction weight, usually expressed as virtual size, and the chosen fee rate, not simply the amount sent. For illustration, a 200-vbyte transaction at 5 sats/vbyte pays 1,000 sats. This is arithmetic, not a current quote; inspect your wallet’s actual estimate before signing.

Each input adds size, depending on its spending conditions. Many small receipts can therefore cost more to spend together than one larger output. An output can become uneconomic to spend at a particular fee rate without becoming invalid or disappearing. Relay-policy dust limits are a different concept; neither creates a universal minimum sensible balance.

Consolidation spends several outputs into fewer outputs you control. It pays a fee now and can reduce input costs later, but future fees are unknown. Combining unrelated histories also publishes evidence linking them. Do not consolidate automatically just because the fee rate is low.

Label outputs first and inspect the selected inputs, destination, change and total fee. Compare two unsigned transaction previews using fictional or practice funds. Keep activities separate where that matters to your privacy; a simpler balance display is not itself a reason to merge them.

Continue your path

One question leads to another.

01Make privacy a routine02Your phone is part of your Bitcoin setup

Find your next answer.

Search the complete field guide · Esc to close