<p>A transaction can have many outputs, hundreds.</p>
<p>Whoever creates that that transaction just has to know the address for each recipient.</p>
<p>Say you set up a business with a thousand employees and paid them in Bitcoin. When you enrol the new employee you could ask them for a Bitcoin address to receive their salary. Each month your payroll program would create one transaction that pays your employees.</p>
<p>Say you are a currency exchange and every day about 1000 customers use your exchange to convert dollars or euros into Bitcoin. At the end of each day you could create one transaction that pays all customers in one go using the payment addresses the customers provided when requesting the currency conversion.</p>
<p>One transaction with a thousand outputs is smaller and therefore cheaper in transaction fees than a thousand separate transactions.</p>

CC BY-SA 4.0
2023-01-17T23:39:41.877Z
Thanks man this makes a lot of sense now!!
madamepresident
CC BY-SA 4.0
2023-01-17T23:20:53.720Z
2023-01-17T23:20:53.720Z
RedGrittyBrick
<p>Many wallets present a sending interface as a single recipient address field and a single amount. The resulting transaction often has two outputs, though. One to pay the recipient and one to send the remainder of your funds back to your own wallet as a change output. However, transactions are not restricted to having one or two outputs. You may actually specify any number of outputs (until your transaction hits the weight limit).</p>
<p><em>Payment batching</em> is especially useful for large enterprises like exchanges and online wallets. Instead of facilitating hundreds of single-payment transactions per day, they may create transactions at a regular cadence to issue all outstanding payments in a single transaction. One exchange I used to work with would for example build a single withdrawal transaction every 15 minutes, which then would pay 5–50 users at once. Another company, a very popular brokerage, even created a transaction every 30 seconds to facilitate some 10–30 payments.</p>
<p>The big advantage of batching payments is that they still only need one change output. If you pay 1000 users per day with single-payment transactions, you send back 1000 change outputs to your wallet that you will have to spend again later. If you send 100 transactions that each batch 10 payments, you only send back 100 change outputs to yourself. Additionally, you need to use at least 1000 inputs to create 1000 transactions, but perhaps most of your batching transactions can be funded with 1–4 inputs. Occasionally, you will even be able to find a few inputs that match the recipient amounts exactly and you will need no change output at all. Overall, batching payments can significantly reduce the cost of operating a large volume wallet, and simplify UTXO management.</p>

CC BY-SA 4.0
2023-01-18T14:23:30.983Z
2023-01-18T14:23:30.983Z
Murch
<p>I have tx hash 5b03738ed2cc9c80e6a4dded10794ab28efca2671039764217d53c54f64a3f39 and it contains 11 outputs. I understand how UTXO works, but where I feel confused is how does the sending address know to create multiple outputs? Like are those receiving addresses all going to the same person? Why is there multiple addresses to begin with? Why not one for the transaction value and then another one for the &quot;change&quot;?</p>
<p>Can someone explain this to me as if I were 5 years old?</p>

<transactions><output><payment-batching>
Explain like I am 5...how can one transaction hash have so many outputs?
madamepresident
# Explain like I am 5...how can one transaction hash have so many outputs?

(Asked by: username_0 on 2023-01-17)

I have tx hash 5b03738ed2cc9c80e6a4dded10794ab28efca2671039764217d53c54f64a3f39 and it contains 11 outputs. I understand how UTXO works, but where I feel confused is how does the sending address know to create multiple outputs? Like are those receiving addresses all going to the same person? Why is there multiple addresses to begin with? Why not one for the transaction value and then another one for the "change"?

Can someone explain this to me as if I were 5 years old?

**Tags:** transactions, output, payment-batching


---

## 2 answers

### Answer by username_1 on 2023-01-17. Score: 4

A transaction can have many outputs, hundreds.

Whoever creates that that transaction just has to know the address for each recipient.

Say you set up a business with a thousand employees and paid them in Bitcoin. When you enrol the new employee you could ask them for a Bitcoin address to receive their salary. Each month your payroll program would create one transaction that pays your employees.

Say you are a currency exchange and every day about 1000 customers use your exchange to convert dollars or euros into Bitcoin. At the end of each day you could create one transaction that pays all customers in one go using the payment addresses the customers provided when requesting the currency conversion.

One transaction with a thousand outputs is smaller and therefore cheaper in transaction fees than a thousand separate transactions.

> **Comments:**
> **username_0**: Thanks man this makes a lot of sense now!!  

---

### Answer by username_2 on 2023-01-18. Score: 0

Many wallets present a sending interface as a single recipient address field and a single amount. The resulting transaction often has two outputs, though. One to pay the recipient and one to send the remainder of your funds back to your own wallet as a change output. However, transactions are not restricted to having one or two outputs. You may actually specify any number of outputs (until your transaction hits the weight limit).

*Payment batching* is especially useful for large enterprises like exchanges and online wallets. Instead of facilitating hundreds of single-payment transactions per day, they may create transactions at a regular cadence to issue all outstanding payments in a single transaction. One exchange I used to work with would for example build a single withdrawal transaction every 15 minutes, which then would pay 5–50 users at once. Another company, a very popular brokerage, even created a transaction every 30 seconds to facilitate some 10–30 payments.

The big advantage of batching payments is that they still only need one change output. If you pay 1000 users per day with single-payment transactions, you send back 1000 change outputs to your wallet that you will have to spend again later. If you send 100 transactions that each batch 10 payments, you only send back 100 change outputs to yourself. Additionally, you need to use at least 1000 inputs to create 1000 transactions, but perhaps most of your batching transactions can be funded with 1–4 inputs. Occasionally, you will even be able to find a few inputs that match the recipient amounts exactly and you will need no change output at all. Overall, batching payments can significantly reduce the cost of operating a large volume wallet, and simplify UTXO management.


---

