1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-02-17 01:52:09 +00:00

Made changes to ch02.asciidoc

This commit is contained in:
myarbrough@oreilly.com 2014-11-05 08:33:29 -08:00
parent 257537e1f4
commit 0ce791e6d7

View File

@ -164,9 +164,7 @@ The response shows one unspent output (one that has not been redeemed yet) under
[TIP] [TIP]
==== ====
Use the following link to look up the transaction from Joe to Alice: View the http://bit.ly/1tAeeGr[transaction from Joe to Alice].
https://blockchain.info/tx/7957a35fe64f80d234d76d83a2a8f1a0d8149a41d81de548f0a65a8a999f6f18
==== ====
As you can see, Alice's wallet contains enough bitcoins in a single unspent output to pay for the cup of coffee. Had this not been the case, Alice's wallet application might have to "rummage" through a pile of smaller unspent outputs, like picking coins from a purse until it could find enough to pay for coffee. In both cases, there might be a need to get some change back, which we will see in the next section, as the wallet application creates the transaction outputs (payments). As you can see, Alice's wallet contains enough bitcoins in a single unspent output to pay for the cup of coffee. Had this not been the case, Alice's wallet application might have to "rummage" through a pile of smaller unspent outputs, like picking coins from a purse until it could find enough to pay for coffee. In both cases, there might be a need to get some change back, which we will see in the next section, as the wallet application creates the transaction outputs (payments).