Where does the change go in a Bitcoin payment?
Why a payment can create an output for the recipient and another for the sender.
The mechanism
Bitcoin spends existing transaction outputs rather than subtracting from a single account balance. If selected inputs exceed the recipient amount and fee, a wallet commonly creates a change output. That output remains under the sender’s control, assuming the wallet constructed the transaction correctly.
Put it into practice
Imagine spending an output worth 100,000 satoshis to make a 60,000-satoshi payment with a 1,000-satoshi fee. A 39,000-satoshi change output balances the transaction. These are illustrative amounts, not a suggested fee. When reviewing a payment, distinguish the recipient output, change and fee. A second address is not automatically a second external recipient. Use the wallet’s own change identification and a trusted device display rather than guessing from an explorer alone.
A second worked example
Suppose a wallet selects two illustrative inputs: 80,000 and 45,000 satoshis. Their combined value is 125,000 satoshis. If the recipient receives 100,000 and the transaction fee is 2,000, the remaining 23,000 can be returned as change. The arithmetic is inputs minus recipient outputs minus the fee; the example does not recommend a fee or tell a wallet which inputs to select.
What an explorer cannot settle for you
A transaction display exposes amounts and addresses, but a label such as change may be an inference. Check the intended recipient and amount against the signing interface before authorising a payment. For bookkeeping, retain the transaction identifier and the invoice reference separately. Never publish recovery material as evidence of ownership.
Keep the evidence in view.
developer.bitcoin.org — source & further reading ↗Checked for this edition on 7 October 2026. Examples are illustrative unless stated otherwise. Read our editorial standards.
Another angle.
The less glamorous Bitcoin update that matters to node operators
Bitcoin Core 29.4’s release notes describe a fix for excessive chainstate disk activity.
Your wallet and your node do different jobs
Key management and transaction validation are separate responsibilities.