Multi-Output Transaction

Overview

A multi-output transaction contains two or more outputs produced by one transaction. Each output defines a value and a spending condition or destination. In Bitcoin-style UTXO systems, the outputs become independently spendable records after confirmation. One output may pay a merchant, another may pay a second recipient, and another may return change to the sender.

Batching payments into one transaction can reduce repeated overhead because common transaction fields and inputs are shared. Exchanges, payroll systems, and merchant payout services use this structure to serve many recipients at once. However, adding outputs still increases transaction size, and the transaction fee must be allocated according to the sender’s accounting policy rather than assumed to belong to one recipient.

Reconciliation is more complex than matching a transaction ID. A single Blockchain Transaction can contain dozens or thousands of outputs, and the same destination can appear more than once. Systems should identify the exact output index, asset, amount, and script or address. They should also exclude change outputs from revenue and verify that the transaction itself executed and finalized.

A multi-output transaction differs from a Multi-Input Transaction, although one transaction can have both. Privacy can be affected because the batch publicly links recipients and may reveal change heuristics. Operational controls should validate every destination before signing, enforce batch limits, and support partial business exceptions even though the on-chain transaction succeeds or fails as one atomic object.

Multi-Output Transaction should be evaluated against the target network’s actual rules, not a familiar label from another system. In this case, a multi-output transaction can deliver many payments efficiently, but reconciliation must track each output rather than treating the transaction ID as one payment. The supporting evidence for Multi-Output Transaction should remain available for review, including the relevant block, transaction, state, or key records.