A Bitcoin transaction is often described as sending coins from one person to another. The protocol does not keep a row called “Alice’s balance” and subtract from it. It records that particular pieces of bitcoin, created by earlier transactions, have been spent, and that new pieces have been created for whoever can satisfy the new spending conditions.
Coins as a chain of signatures
The Bitcoin white paper defines an electronic coin as a chain of digital signatures. Each owner transfers the coin by signing a hash of the previous transaction and the next owner’s public key, and appending that signature. Later software generalized that idea into scripts, but the structure is the same: a transaction points at earlier outputs and authorizes a new set of outputs.
Those outputs are called unspent transaction outputs, or UTXOs, once they have been created and not yet spent. A wallet balance is the wallet’s sum of UTXOs it believes it can spend. The network does not store that sum as a separate field that the transaction then edits.
Inputs, outputs, and the fee
An input names a previous output, usually by the transaction that created it and the output’s position in that transaction. It also carries whatever data the previous output’s conditions require, often a signature. An output states an amount and a new condition, often “pay to this address,” which in practice means “pay to a script that this key can unlock.”
The amounts have to add up. The sum of the input amounts must be at least the sum of the output amounts. The difference is the transaction fee. There is no separate fee field that the network has to trust. Miners may claim that difference in the block’s coinbase transaction, together with the block subsidy, if the block is valid.
The featured image draws the fee as its own box beside the payment and the change. That box is not a transaction output. The fee is the difference between the sum of the inputs and the sum of the outputs, and a miner may claim it in the coinbase.
If you hold a single output of 0.4 BTC and you want to pay 0.1 BTC, the transaction typically has two outputs: 0.1 BTC to the recipient, and about 0.3 BTC back to an address you control, minus the fee. That second output is the change. Ignoring change is how people accidentally overpay a fee or misread a payment.
What does not move
The transaction does not update a profile, a username, or an account nickname. Addresses are encodings of locking scripts, not accounts with a stored balance. It also does not guarantee that a merchant has received an irreversible payment. Confirmation is a property of the blocks built on top of the block that includes the transaction, not a field inside the transaction itself.
A transaction can fail to be mined. Nodes may keep it in memory, drop it, or replace it under their own policies. Until a block that nodes accept contains the transaction, the new outputs are not in the confirmed set. Another transaction may already be competing to spend the same inputs.
What a careful reading looks like
Read the inputs and ask which older outputs they consume. Read the outputs and ask who can spend each new piece, and whether one of them is your change. Then subtract. The gap between inputs and outputs is the fee, whether or not a wallet labeled it clearly. That is the change a Bitcoin transaction actually makes: it retires specific outputs and writes new ones.
Why the same coins cannot be spent twice in one race
An output can be named by more than one unconfirmed transaction. Nodes and miners then have a conflict to resolve, because a valid block can include only one spend of that output. The other transaction becomes invalid as soon as the first is confirmed. This is the double-spend problem the white paper is organized around, and it is also the ordinary reason a merchant waits for confirmations. A broadcast is a request. A confirmation is a block that spent the output under rules the node accepts. Until then, “the money has been sent” means a transaction exists somewhere, not that the recipient’s output exists for everyone.
Replacement policies, including the replace-by-fee behavior described in BIP 125, let a node prefer a conflicting transaction that pays a higher fee. That policy is not universal, and it is not a consensus rule that every miner must follow. It is another reminder that an unconfirmed transaction is not a settled edit. The settled edit is the block that consumes one set of outputs and creates another. Everything a wallet shows before that block is a prediction about which edit will win.
Sources
- Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System, especially the discussion of transactions.
- Bitcoin Developer Reference: transactions.
- Bitcoin Developer Guide: transactions.
- BIP 125, Opt-in Full Replace-by-Fee Signaling.




