How does the mechanism work?
A wallet may generate a fresh destination for change instead of reusing the receiving address associated with an input. That new destination does not mean the remainder was sent to a new owner.
The transaction records new amounts and scripts. It does not attach a universal “change” tag. A wallet recognises its own change through the destinations and keys it manages; outside observers may make guesses from transaction patterns.
Follow the change into a later transaction to test your mental model. The earlier change output becomes a normal referenced input. Its history as a remainder does not give it a special discount, priority or expiry. The later transaction must satisfy its script and account for its full amount like any other output. A wallet can identify that it controls the destination and include it in its available balance. Outside observers do not receive the wallet’s private classification. This separation between protocol records and wallet bookkeeping explains why a diagram can show exact value conservation without proving which human owns each output.
What would you see in an example?
Imagine you received an output that is larger than today’s payment. The wallet selects it as an input, sets the recipient amount and accounts for the fee. It then creates another output for the remainder. When you later pay again, that change output can become an input to the later transaction.
How do payment, fee and remainder stay in balance?
Use an invented selected input worth 150,000 satoshis. You want to create a payment output worth 100,000 satoshis. If the completed transaction measures 140 vbytes and the illustrative fee rate is 4 sat/vB, the fee is 560 satoshis. The change output is therefore 49,440 satoshis. Payment plus change plus fee exactly equals the selected input value.
The conversion between BTC and satoshis is fixed: 100,000,000 satoshis per BTC. Integer units make this balance easier to inspect than rounded decimal display values. Do not subtract a fee twice. If the recipient output is fixed, the fee is already accounted for in the smaller remainder. An interface that subtracts fees from the recipient amount describes a different construction.
Compare a transaction without change. With the same 150,000-satoshi input and a single 100,000-satoshi output, the remaining 50,000 satoshis are the fee. They do not automatically come back later. There is no implicit refund rule that creates a missing output. The outputs explicitly state which amounts can be spent after the transaction confirms.
Creating change also adds output data and leaves an output that may cost weight to spend later. That trade-off belongs to transaction construction and policy, rather than the consensus definition of change. This lesson deliberately gives no universal small-change cutoff. Different output types and local policies require different context, and a future spending cost cannot be known from today’s payment amount alone.
Common misunderstandings
A new address in the output list need not be an unfamiliar recipient. It may be a destination the sender generated for change. An outside observer can attempt to infer which output is change, but that guess is not a tag stored by the protocol.
A large wallet balance does not mean all of it participates in each payment. Unselected outputs remain separate and unspent. Inspect the selected input total when checking payment arithmetic; comparing only the overall balance before and after can hide unrelated outputs or pending transactions.
Check yourself
With inputs of 60,000 satoshis, payment of 45,000 and fee of 500, how much change is created?
Reveal the answer
14,500 satoshis, if the transaction includes that change output. These invented amounts satisfy inputs = payment + change + fee.
What does this diagram leave out?
Not every transaction creates change. The inputs may match the outputs and fee, or a remainder may be too small to make another output practical under local policy. Before authorising a transaction, distinguish the recipient amount, any returned remainder and the fee. A displayed balance can also include other outputs untouched by this payment.
Which primary sources explain the rules?
Sources: Transaction developer reference; Public-key cryptography reference.
Sources: Output amounts and fee accounting.