Bitcoin UTXOs: a balance is made of spendable outputs

Explainer6 min read

Follow two Bitcoin UTXOs through a fictional payment. Reconcile inputs, outputs and fees, and learn why an unspent record is not proof your wallet can sign.

Fictional Bitcoin UTXO comic: Brokzi checks two selected old outputs against a transaction with two new outputs. A separate fee calculation is the difference between totals, not a third output. No real addresses, signatures or transfers.
AI-assisted editorial illustration · Brokzi
On this page

A wallet shows 75,000 sats. Under that total there might be two UTXOs, worth 30,000 and 45,000 sats, rather than one record with a balance you can partly debit.

For anyone reading a native Bitcoin payment, the useful question is which earlier outputs it spends and which new outputs it creates. This explainer follows that inventory. Our change-address guide separately explains why a remainder may appear at an unfamiliar address.

A UTXO has an identity as well as an amount

UTXO means unspent transaction output. The Bitcoin Developer Guide describes an input as a reference to a particular earlier output. That reference combines the earlier transaction's ID, or txid, with its output index, often called vout. Indexing starts at zero.

Bitcoin Core's 31.1 transaction definitions model that combination as an outpoint. They separately define the input's previous outpoint and the output's value and spending script. An address alone is not an outpoint: it does not identify which transaction and which numbered output you mean.

An amount also has spending conditions. Knowing that an output exists is different from being able to satisfy them. The example below assumes ordinary confirmed, non-mining outputs that the sender can spend, with no extra timing restriction.

Start with two outputs, not two accounts

These are fictional inventory labels, not usable transaction IDs, addresses or instructions to send funds. All amounts are in satoshis, abbreviated sats. Assume no other wallet activity during either scenario. We invent the fee for arithmetic; it is not a current rate or wallet quote.

Starting outputValueAssumed control
TX-A:030,000 satsSender can spend it
TX-B:145,000 satsSender can spend it
Combined inventory75,000 satsSum of these two outputs

The colon labels mean "transaction label, output index" only for this example. Two outputs from the same transaction would share its transaction ID but have different indexes. Two unrelated payments to an address would not become one output merely because their destinations match.

The 75,000-sat total does not decide the input selection. That happens when a wallet constructs a particular transaction. You need the actual selected outpoints to understand what it proposes to spend.

A 50,000-sat payment uses both inputs in our example

Assume the wallet selects both starting outputs for one ordinary payment. Their full 75,000-sat value funds two new outputs:

New transaction componentValueRole
TX-C:050,000 satsRecipient output
TX-C:124,000 satsChange controlled by the sender
Total output value74,000 satsSum of those two outputs

The fee is the difference:

30,000 + 45,000 − 50,000 − 24,000 = 1,000 sats

There is no TX-C:2 fee output in this example. Nor does either old output retain a smaller spendable remainder. Once this transaction confirms on the active chain, the two selected old outputs are spent; the sender's remainder is the new 24,000-sat change output. This follows the guide's whole-output spending and fee accounting, not a physical cutting of coins.

The inventory has changed. The sender began with two outputs and ends with one from this transaction; the recipient receives a separate output. For the narrower question of identifying that change as your own, use the wallet-aware checks in the linked change-address article, not an explorer's guess about ownership.

A smaller payment can leave an old UTXO untouched

Use a separate alternative, starting again with the original two outputs. Suppose a 20,000-sat payment selects only TX-A:0. With an invented 1,000-sat fee, it creates a 20,000-sat recipient output and a 9,000-sat change output.

30,000 − 20,000 − 9,000 = 1,000 sats

The unselected TX-B:1 still represents 45,000 sats. The sender's remaining inventory is 45,000 + 9,000 = 54,000 sats, rather than one reduced version of the original 75,000-sat record.

These are alternative transactions, not two payments we execute sequentially. The shared fee amount keeps the comparison simple; it does not imply equal transaction size or fee rate. The RBF and CPFP explainer covers virtual-size and fee-rate accounting, and why changing a pending payment is a different task from choosing its inputs.

Unspent is not a complete wallet-availability check

Bitcoin Core's 31.0 listunspent reference documents filters for confirmations and output amounts. A list produced with particular filters is not necessarily every output represented by a wallet's headline total.

Read the fields in that version carefully. It marks spendable deprecated and always true. Its solvable field concerns knowing how an output could be spent while ignoring missing keys. Neither field alone proves that the particular wallet can complete a signature now.

The documented safe field is a wallet spending-policy classification, including treatment of certain unconfirmed transactions. It is not an asset-safety rating or a promise of confirmation. Do not transfer these version-specific field definitions to every wallet app.

An exchange's internal account balance is a different record again. This article explains native Bitcoin transaction structure, not a customer's control over an exchange's withdrawal inputs, Lightning balances or BTC represented on another network.

A node's unspent view needs context

The 31.0 gettxout reference looks up an outpoint and returns its value, script information and confirmation context when found. Its default includes the node's mempool: an output spent by a transaction in that mempool does not appear in the result.

That is not the same claim as "this spend is confirmed everywhere." A null result says the lookup did not find the output in that view; it does not establish the cause by itself. Check the outpoint, the node's state and the lookup's settings before interpreting an absent result. We have not run either RPC or connected to a Bitcoin node.

The confirmation explainer separates active-chain inclusion, reorganisations and account credit. A screenshot of an unspent list does not replace those checks.

Read the inventory before the headline total

Keep the exact outpoints, their amounts and the selected inputs together. Total all new outputs, reconcile the difference as the fee, and identify what the wallet still controls. Keep signing ability, pending status and confirmation separate from that arithmetic.

The UTXO model explains why the same displayed balance can be assembled from different sets of outputs. It does not tell you which outputs to consolidate, what fee to pay or whether a transaction is safe to sign. Following this example requires no wallet connection, recovery phrase or transfer.

Sources

Primary documents checked 20 October 2026 (Asia/Tbilisi). The guide includes historical policy passages; this article uses its basic output model, not its old fee thresholds, script popularity claims or transaction-size policy. Core examples are explicitly scoped to 31.0 RPC documentation and 31.1 source definitions, not a claim about all current wallets. All transaction labels and amounts are fictional. No node, wallet, signature or transfer was tested.

See something wrong? Brokzi logs material changes. Prepare a correction note.

About the byline

Brokzi Editorial

The accountable byline for Brokzi’s explainers, definitions, news notes, and corrections.

Editorial responsibility →