mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-30 03:48:31 +00:00
Edited ch03.asciidoc with Atlas code editor
This commit is contained in:
parent
b104a39cca
commit
20a4b08c5e
@ -615,9 +615,9 @@ We can further explore the blockchain by examining the previous transaction refe
|
|||||||
|
|
||||||
==== Exploring Blocks
|
==== Exploring Blocks
|
||||||
|
|
||||||
Commands: +getblock+, +getblockhash+
|
((("Bitcoin Core", "Bitcoin Core API", "exploring blocks")))((("blocks", "exploring with Bitcoin Core API")))Commands: +getblock+, +getblockhash+
|
||||||
|
|
||||||
Exploring blocks is similar to exploring transactions. However, blocks can be referenced either by the block _height_ or by the block _hash_. First, let's find a block by its height. In <<cup_of_coffee>>, we saw that Alice's transaction was included in block 277316.
|
((("blocks", "block height")))((("blocks", "block hash")))Exploring blocks is similar to exploring transactions. However, blocks can be referenced either by the block _height_ or by the block _hash_. First, let's find a block by its height. In <<cup_of_coffee>>, we saw that Alice's transaction was included in block 277316.
|
||||||
|
|
||||||
We use the +getblockhash+ command, which takes the block height as the parameter and returns the block hash for that block:
|
We use the +getblockhash+ command, which takes the block height as the parameter and returns the block hash for that block:
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user