A Bitcoin transaction can pay several recipients, so one transaction identifier can legitimately appear in several payment records. To find your receipt, match the output to your expected receiving address and record its amount and output index. The transaction's total output value is not necessarily the amount paid to you, and another recipient's presence does not make your own payment invalid.
Find the output that answers your question
Open the transaction in a trusted Bitcoin explorer and expand its outputs. Compare the complete receiving address with the one you supplied for this payment. Record the index and amount of the matching output. If the same address appears more than once, record the relevant outputs individually rather than assuming the first matching row is the whole receipt. Do not choose an output solely because its amount resembles your request.
Bitcoin's transaction reference describes a transaction's inputs and outputs, while Bitcoin Core's versioned getrawtransaction reference exposes output details and their indices. A transaction identifier narrows the record; the index narrows the particular output within it. Our UTXO guide explains why those two pieces are used together to identify an output.
Read this fictional receipt without claiming the whole batch
Suppose an ordinary fictional transaction spends inputs totalling 200,000 sats and creates the three outputs below. Your independently verified receiving address matches output 0. The other rows are not yours merely because they share the same transaction. The labels are descriptive placeholders, not real addresses or evidence about who controls the other outputs.
| Output index | Destination evidence | Amount | Your conclusion |
|---|---|---|---|
| 0 | Matches your expected address | 40,000 sats | This is the matching receipt in the example |
| 1 | A different address | 90,000 sats | Do not add it to your payment |
| 2 | Another address with ownership unestablished | 66,000 sats | Do not assume who owns it |
| Output total | All three outputs | 196,000 sats | The transaction-wide total, not your individual receipt |
| Network fee | 200,000 minus 196,000 | 4,000 sats | The fee of this transaction as a whole |
The arithmetic establishes a 40,000-sat matching output and a 4,000-sat transaction fee under the example's assumptions. It does not establish that your service charged you 4,000 sats or that you should receive 196,000 sats. A service's withdrawal quote and internal charges must be reconciled with its own record. Keep the quoted net amount separate from the network-wide fee.
Output 2 may be change, another payment or another arrangement; the sample does not establish its owner. Do not turn an explorer's visual grouping into certainty about every participant. The example is designed to let you verify your own receipt without naming the other outputs or inventing a customer list. If a service supplies a specific output index, compare it with the address and amount rather than accepting the index without checking.
A shared txid is compatible with separate customer records
Bitcoin Core's sendmany documentation is a concrete example of supplying multiple destinations and amounts in one wallet operation. This explains the technical possibility of multiple payment outputs without asserting that a particular exchange uses that command. A service can associate different internal requests with different outputs of the same public transaction.
That relationship also explains why a support agent may need your own withdrawal or order reference. The txid identifies the shared transaction, while the service record establishes which payout was intended for you. Send both, plus the matching output index if known. Do not submit another customer's reference or conclude that a repeated txid must be a copied fake simply because someone else can show it.
There is an important limit: many outputs alone do not prove an exchange batch or several unrelated owners. A wallet can also make transactions involving its own addresses. Describe the observed output structure and your verified match. Treat the business reason for the other outputs as unknown unless the sender provides reliable evidence.
Confirmation and spend status answer different questions
The outputs belong to the same transaction inclusion, but each can later be spent independently. An explorer marking your output as spent does not erase its original receipt. Follow the later spend if you are reconciling current availability. Conversely, finding the output in an unconfirmed transaction does not establish the final settlement or service-side crediting required by the recipient.
The mempool.space reading guide helps locate transaction status and output details. Keep the observation time when saving evidence because confirmation state and later spends can change. If you are asking about current wallet balance, use the current unspent state; if you are proving historical delivery, retain the original output and its confirmation evidence. These are related records with different purposes.
Resolve a mismatch by pointing to the exact row
- Save the sender's withdrawal or payment reference and supplied txid.
- Confirm that the explorer is showing the intended Bitcoin network.
- Compare the complete expected address with the outputs.
- Record every relevant matching output, its index and amount.
- Check the transaction's status and distinguish historical receipt from later spending.
- Explain any address or net-amount mismatch to official support using the specific output evidence.
If no output matches, do not select the closest-looking amount and call it your receipt. Ask the sender to reconcile the intended destination and the identifier it supplied. If a matching output exists but the receiving service has not credited it, give that service the output evidence and its own order reference. The presence of other payouts does not explain every missing credit, so state the actual discrepancy.
For a no-account swap, compare your matching output with the current order's amount and address instructions. Do not treat the batch total as a deposit or send another payment merely because the explorer's headline is larger than your order. Your evidence should identify the particular value delivered to the intended destination, with the rest of the transaction retained as context.
Bitcoin Core's wallet transaction reference also distinguishes wallet-related transaction details from the entire raw transaction. Remember that scope when comparing a wallet app's number with an explorer total. A difference in scope can explain the two displays without either being an arithmetic error.
FAQ
Why can a Bitcoin transaction have multiple outputs?
One transaction can create several outputs for payments, change or other wallet purposes. Their existence does not by itself establish how many unrelated owners are involved.
How do I find my payment in Bitcoin batch transactions?
Match the expected receiving address and amount, then record the output index with the txid. Keep your own service reference so support can associate that output with the intended payout.
Does a Bitcoin output marked spent mean the payment never arrived?
No, a later spend does not remove the historical receipt. Use the original output to prove delivery and the later spending record to explain current availability.