Skip to content

Commit bb15701

Browse files
Edited the output to include the array brackets.
1 parent 4c81b3e commit bb15701

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

08_1_Sending_a_Transaction_with_a_Locktime.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Once you've figured out the current height, you can decide how far in the future
4242

4343
Once you have figured out your locktime, all you need to do is write up a typical raw transaction, with a third variable for `locktime`:
4444
```
45-
$ rawtxhex=$(bitcoin-cli -named createrawtransaction inputs='''[ { "txid": "'$utxo_txid'", "vout": '$utxo_vout' } ]''' outputs='''{ "'$recipient'": 0.001, "'$changeaddress'": 0.00095 }''' locktime=1774650)
45+
$ rawtxhex=$(bitcoin-cli -named createrawtransaction inputs='''[ { "txid": "'$utxo_txid'", "vout": '$utxo_vout' } ]''' outputs='''[{ "'$recipient'": 0.001, "'$changeaddress'": 0.00095 }]''' locktime=1774650)
4646
```
4747
Note that this usage of `locktime` is under 500 million, which means that it defines a block height. In this case, it's just a few blocks past the current block height at the time of this writing, meant to exemplify how locktime works without sitting around for a long time to wait and see what happens.
4848

0 commit comments

Comments
 (0)