A Bitcoin transaction can show more than one destination even when someone intended to make a single payment. One output may pay the recipient, while another returns the unused portion to the sender’s wallet.
This is easier to understand when you separate a wallet’s displayed balance from the individual unspent transaction outputs, or UTXOs, that it can use. The Bitcoin Developer Guide explains transaction inputs, outputs and change. An input spends an existing output in full; the new transaction allocates the value into new outputs and a fee.
Follow a small worked example
Suppose a wallet selects one input worth 100,000 satoshis. In this illustrative transaction, it creates a 60,000-satoshi payment output and a 39,000-satoshi change output. The remaining 1,000 satoshis form the transaction fee.
The arithmetic is 100,000 minus 60,000 minus 39,000, leaving 1,000. These figures explain the structure; they are not a suggested fee or a prediction of what a wallet will choose.
The change output can use another address controlled by the same wallet. It does not have to return to the exact address associated with the input. A wallet may also select several inputs or create a transaction without a change output, so this example is only one possible arrangement.
Read an explorer without assuming ownership
On a block explorer, distinguish the transaction’s total inputs from the amount paid to the intended recipient. Adding every output together and describing that sum as the payment can misrepresent what happened.
However, a public transaction alone does not necessarily tell you who controls each address. Treat a suggested change label as an interpretation unless you have independent wallet information. Do not assume that the larger or smaller output must always be the change.
For your own records, compare the wallet’s transaction detail with the intended payment, fee and remaining balance. If something is unclear, consult the wallet’s official documentation before moving funds again. A request to reveal a seed phrase or private key is not a legitimate step in explaining a change output; those secrets should not be entered into an explorer or sent to someone offering to inspect the transaction.