Change Output

Overview

In a UTXO transaction, selected inputs are consumed completely. If their total value exceeds the intended payment plus fee, the wallet creates a Change Output for the remainder. The output becomes a new UTXO controlled by the sender and can be spent in a later transaction.

The wallet’s Coin Selection algorithm influences whether change is needed and how large it is. Selecting inputs close to the target can reduce change, but privacy, fee efficiency, and future spend cost also matter. If the remainder is too small to spend economically, the wallet may add it to the transaction fee instead of creating dust.

Change can confuse observers because it is not explicitly labeled on-chain. Analysts use heuristics to guess which output returns to the sender, but modern wallets can choose output ordering and scripts that reduce certainty. A merchant should never assume that every nonpayment output belongs to the customer without additional evidence.

Wallets commonly send change to a newly derived address rather than reusing the original sending address. This improves privacy and fits hierarchical deterministic wallet management, but it creates a backup requirement: the wallet must be able to recover the change key. Exporting only one visible address can leave change funds inaccessible.

For support and reconciliation, the payment amount should be matched to the correct recipient output, not to the total transaction value. The transaction fee is the difference between total inputs and total outputs. Understanding change prevents a common mistake in which a user or analyst interprets the sender’s returned value as a second payment. Fee planning also depends on the resulting Virtual Byte (vByte) size, because an extra output increases transaction weight and can make very small change uneconomical.