From 0ce791e6d711f7b9c600f8541e32747939d55115 Mon Sep 17 00:00:00 2001 From: "myarbrough@oreilly.com" Date: Wed, 5 Nov 2014 08:33:29 -0800 Subject: [PATCH] Made changes to ch02.asciidoc --- ch02.asciidoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/ch02.asciidoc b/ch02.asciidoc index f931d357..4ab9ecd6 100644 --- a/ch02.asciidoc +++ b/ch02.asciidoc @@ -164,9 +164,7 @@ The response shows one unspent output (one that has not been redeemed yet) under [TIP] ==== -Use the following link to look up the transaction from Joe to Alice: - -https://blockchain.info/tx/7957a35fe64f80d234d76d83a2a8f1a0d8149a41d81de548f0a65a8a999f6f18 +View the http://bit.ly/1tAeeGr[transaction from Joe to Alice]. ==== 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).