Could someone explain how the TX operation here works?

Multiple outputs are usual, just like e-mail.
If one of your friends has sent you 5 BTC, and another friend has sent you 2 BTC, you should combine and spend them if you need to buy something for less than 7 BTC and greater than 5 BTC.

(By the way, do you know what a change is?)

There is no "This output gets its value from this input" All input values are summed, then spent.

MCCCS

Posted 2018-03-18T05:23:00.757

Reputation: 5 827

Thank you for the link to Change. I was aware of it, but the link provided a much better explanation.

If all inputs are summed, do we assume that all inputs are from the same account holder/entity? – EvilJordan – 2018-03-18T07:18:24.357

@EvilJordan No, take a look at SIGHASH_SINGLE. It's how CoinJoin works. For more information: https://en.bitcoin.it/wiki/CoinJoin

– MCCCS – 2018-03-18T07:37:09.627

Thanks for walking me through this. I thought I understood how this worked, but it's suddenly become a lot more complex. So, from what I gather, if Bob has 2 BTC and wants to send Alice 1 BTC, somehow Tom, with his 1 BTC he wants to go to Jane can also get in the mix, and a transaction will show two inputs (Bob:2, Tom:1) and three outputs (Alice:1,Bob(change):1,Jane:1). I guess my question is how did Tom's transaction to Jane end up in the mix? Is the software doing that to save on bandwidth? – EvilJordan – 2018-03-18T07:57:46.667

@EvilJordan Oops, CoinJoin uses SIGHASH_ALL. If you're looking for how CoinJoin works, here's the answer. https://bitcoin.stackexchange.com/a/57276/38618

– MCCCS – 2018-03-18T08:33:55.013

Did you initially bring up CoinJoin because this particular transaction I referenced is using it? Seems like a very niche service. – EvilJordan – 2018-03-18T17:46:41.683

Could someone explain how the TX operation here works?

Answers