Articles on: Bitcoin Wallets

Use Sparrow coin control, labels, and UTXO freezing safely

A Bitcoin wallet balance is made of separate unspent transaction outputs, or UTXOs. When you spend a UTXO, the transaction consumes it in full. Any value not sent to the recipient or paid as a fee usually returns to the wallet as a new change output.

Avoid accumulating too many small UTXOs in your wallet. As Bitcoin's value increases and on-chain fees fluctuate, these small UTXOs can become uneconomical to spend, potentially costing more in transaction fees than the value they hold.
Consolidating smaller UTXOs into a reasonable size during periods of lower network fees is good wallet hygiene. Review your UTXOs regularly and consolidate when it makes economic sense, while considering the privacy implications of combining multiple UTXOs in a single transaction.

Sparrow’s coin-control tools let you decide which UTXOs a transaction will consume. That control can help you avoid linking unrelated activity, preserve a coin for later, or plan fees. It can also damage privacy if you select inputs carelessly. Combining several UTXOs in one transaction commonly gives outside observers a reason to assume that one owner controlled them all.

This guide assumes your wallet is already set up and synchronized. It does not cover ordinary sending or promise anonymity.

Stop before signing if the selected inputs combine contexts you meant to keep separate, if change is unexplained, or if you cannot identify why each input was selected. Cancel the transaction and start again from the UTXOs tab.

Follow the executed regtest example

The following Sparrow 2.5.3 walkthrough used four confirmed regtest UTXOs. Three outputs shared one receive address, allowing the test to demonstrate address-level labeling, freezing, exclusion, unfreezing, deliberate selection, and change review without spending real bitcoin.

Diagram showing that a transaction consumes complete UTXOs and creates separate recipient, change, and fee outputs

1. Inventory and label the outputs

Open UTXOs and treat every row as a separate coin. Record the output reference, value, confirmation state, and existing label before making a selection.

Sparrow Unspent Transaction Outputs inventory showing four separate confirmed regtest outputs

In Sparrow 2.5.3, edit a label by opening Addresses, locating the receive or change address that owns the output, and double-clicking its Label cell. Enter a neutral category and press Enter. The executed label, Coin control test set, persisted after navigating away and back.

A saved neutral label on the receive address owning three coin-control test UTXOs

2. Freeze and prove exclusion

On Addresses, right-click the address or outpoint you intend to hold and choose Freeze UTXOs. If the address owns multiple unspent outputs, this address-level action freezes all of them; confirm the exact rows before continuing.

Sparrow address context menu with Freeze UTXOs for the selected receive address

The executed address owned 0.05, 0.06, and 0.07 BTC outputs. After freezing them, an automatic 0.68 BTC spend used the separate 0.69999433 BTC output as its only input. The three frozen outpoints were absent from the transaction input tree. The transaction was closed before signing.

Transaction editor showing one available input while the three frozen outputs are excluded

Return to Addresses, review the label and reason for the hold, then right-click the same address and choose Unfreeze UTXOs. Reopen UTXOs and confirm the rows are eligible again.

Sparrow address context menu showing Unfreeze UTXOs for the labeled test set

3. Select inputs and review change

Select one intended row. Ctrl-click on Linux or Windows, or Cmd-click on macOS, only when you deliberately want another input. The test selected the 0.05 and 0.06 BTC outputs; Sparrow displayed 2/4 and Send Selected (11,000,000 sats).

Two intended UTXOs selected together with Send Selected showing their total

Use Clear whenever you need to restart. The empty Send screen proves the prior selected-input set no longer remains in the draft.

Sparrow Send screen after Clear removed the selected UTXOs and draft details

Reselect the intended rows and choose Send Selected. Enter the destination, amount, and fee. Before creating the transaction, confirm the input graph still contains exactly the selected rows and that Clear (2 UTXOs selected) is available.

Send Selected hands the two chosen UTXOs to the transaction builder and shows payment, change, and fee

The resulting unsigned transaction contained exactly two inputs, a 0.10 BTC external payment, a 0.00999707 BTC wallet change output, and the fee. Review this tree before Finalize Transaction for Signing; the test closed the draft without signing or broadcasting.

Unsigned coin-control transaction review with two inputs, external payment, change, and fee

Combining inputs can connect their histories publicly. Do not call consolidation a privacy improvement.

Diagram comparing a same-context spend with a transaction that links two previously separate contexts

Read the UTXO list as an inventory

Open the wallet’s UTXOs tab. Sparrow labels this view Unspent Transaction Outputs. Each row represents a spendable output known to the wallet, subject to confirmation and wallet settings.

Treat the list as an inventory rather than a single balance. Two outputs of the same value may have very different histories and privacy implications. One may be associated with a public donation address, another with an exchange withdrawal, and another with a private transfer. Spending them together can connect those histories on-chain.

Do not share a screenshot of this screen. Output references, addresses, values, dates, labels, and balances can reveal wallet activity even though they are not private keys.

Add useful labels at receipt

Labels work best when you add them while you still remember why a payment arrived. Use short categories that help with future selection, such as a broad purpose or accounting period. Avoid names, account numbers, street addresses, order details, or anything that would cause harm if the wallet file or a screenshot leaked.

A label is local wallet metadata. It is not written into the Bitcoin transaction, and restoring only a signer backup may not restore Sparrow’s labels. Include wallet files or a supported label export in your separate application-data backup plan.

A good label answers the future spending question without becoming a customer database. For example, a neutral category can remind you that two outputs share the same context. It does not need to identify the person or service involved.

Review labels before relying on them. A stale or ambiguous label is worse than no label if it causes you to merge unrelated activity. If you are uncertain about an output’s history, leave it unselected until you can confirm it from records you control.

Freeze a UTXO you do not want selected

To keep Sparrow from treating an output as spendable, open Addresses, locate the receive or change address that owns it, right-click that row, and choose Freeze UTXOs. If several outputs use the same address, this freezes every unspent output on that row. Expand or cross-check the row against UTXOs before applying the action. Sparrow excludes frozen outputs from automatic spendable selection. The rows remain part of the wallet; freezing does not move the bitcoin or create an on-chain transaction.

Freezing is useful for a reserve, a disputed payment, an output awaiting more confirmations, or any coin you want to inspect before use. Add or update its label so you remember why it is frozen.

Freezing is only a control in the local wallet data. It is not an on-chain lock, does not stop another wallet with the same signing authority from spending the output, and does not protect keys. A restored wallet may not carry the frozen state unless the relevant Sparrow data or label format was preserved and restored correctly.

Sparrow 2.5.3 was tested both ways with the same frozen 19,994,961-sat regtest output. Opening a portable Sparrow wallet export restored the wallet and labels but did not restore the freeze: the row offered Freeze UTXOs again.

Portable Sparrow wallet export restored without the prior frozen-output state

A direct wallet-database copy made only after Sparrow had fully exited did preserve the freeze. In the clean profile, the same row offered Unfreeze UTXOs. Treat closed data-directory copies and portable wallet exports as different backup layers, and always audit frozen outputs after recovery.

Direct closed-wallet file copy restored with the frozen-output state intact

The restored direct copy also rejected a 1,000-sat automatic spend as Insufficient funds even though the wallet displayed a 19,994,961-sat balance. No input or fee was selected and Create Transaction remained disabled, confirming that the restored freeze affected selection rather than only its icon.

Restored direct copy excluding the sole frozen UTXO from automatic selection

Use Unfreeze UTXOs only after you have reviewed the reason for the freeze and the transaction you are about to make.

Stop if an output you intended to freeze still appears in automatic input selection. Cancel the transaction, confirm that the freeze was applied in the wallet you are spending from, and retest before using meaningful funds.

Select inputs deliberately

On the UTXOs screen, select the output you intend to spend. Use Ctrl-click on Windows or Linux, or Cmd-click on macOS, to select more than one. Then choose Send Selected.

Sparrow also provides Select All and Clear. Clear is useful when you need to restart the decision. Treat Select All with caution. Selecting every output is a consolidation decision, not a harmless shortcut.

Before continuing, ask whether the selected UTXOs already share a public context. If they do not, combining them creates a new visible connection. Separate transactions may preserve separation, though they may cost more in total fees. There is no universal answer: the decision depends on the payment, current fees, future spending plans, and the privacy history of the outputs.

Avoid spending unconfirmed outputs by default. Their availability can depend on Sparrow settings and the status of the parent transaction. Waiting for confirmation reduces transaction-chain complexity and the chance that a parent problem affects your new spend.

Review change and fees

The transaction editor should show the selected inputs, external outputs, fee, and any change output. Confirm that the inputs match the rows you chose. If Sparrow adds another input, determine why before proceeding; the selected value may not cover the payment and fee.

Change matters because spending it later can reveal more of the wallet’s history. Confirm that the change output belongs to the intended wallet policy. When using a hardware signer, verify outputs and change recognition on its trusted display before authorizing.

A consolidation can reduce the number of inputs needed in a later transaction, but it links the consolidated outputs now. It may also be expensive when fees are high. Do not describe consolidation as a privacy improvement. It is an operational choice with an immediate on-chain footprint.

Stop if there is an external output you do not recognize, the payment amount is wrong, the fee is unacceptable, the signer does not recognize change, or the input list changed after your review. Reject the signing request and rebuild the transaction.

Keep labels and freeze states usable

Review frozen outputs periodically. Confirm that each freeze still has a reason and that labels remain accurate. Remove outdated personal detail rather than letting the wallet become a permanent store of sensitive records.

Back up the application data needed to preserve labels separately from signer or seed backups. If you use an export format, test the round trip with a copy of the wallet before depending on it. Store exports privately; a label file can expose addresses, transaction references, and the relationships you were trying to protect.

After a Sparrow update, test a small controlled selection: freeze one disposable output, confirm automatic selection excludes it, unfreeze it, select known inputs, and verify the transaction editor preserves your selection. Do not assume a visible freeze icon alone proves the complete spending behavior you expect.

Coin control works when every transaction starts with a purpose. Select only the inputs needed for that purpose, verify what Sparrow constructed, and let the signer’s display make the final check before approval.

Connect Sparrow to your own Bitcoin Core node
Speed up or cancel an unconfirmed Sparrow transaction with RBF or CPFP

Official Sparrow sources

Updated on: 14/10/2026

Was this article helpful?

Thank you!