getblock

getblock returns the contents of a Bitcoin block identified by its hash, and a verbosity argument lets you choose exactly how much detail you pay for: 0 gives the raw serialized block as hex, 1 gives a decoded object with the list of txids, 2 expands every transaction into a full object with fee data, and 3 (Bitcoin Core 25.0+) adds the spent prevout — value and script — for each input. This is the workhorse for reading the BTC transactions packed into a block roughly every ten minutes. Send the block hash and your chosen verbosity as positional parameters to https://bitcoin.therpc.io/YOUR_API_KEY.

Use cases

• List the txids in a block at verbosity 1 to feed an indexer cheaply.
• Pull full transaction objects, with fees, in a single call at verbosity 2.
• Read each input's prevout — the spent value and script — at verbosity 3 without extra lookups.
• Fetch the raw serialized block at verbosity 0 when you want to hash or verify it yourself.

Parameters

Response

Example request

1curl https://bitcoin.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5  "jsonrpc": "1.0",
6  "id": "therpc",
7  "method": "getblock",
8  "params": [
9    "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
10    1
11  ]
12}'

Errors & troubleshooting

Common pitfalls

• Verbosity 2 and 3 are heavy: a full block can hold thousands of BTC transactions, so the JSON payload gets large and providers may rate-limit or slow those requests.
• Verbosity 3 requires Bitcoin Core 25.0+ and an unpruned best-chain block, and not every provider passes it through — fall back to verbosity 2 plus per-input lookups if it errors.
• You pass a block hash here, not a height, so resolve a height to its hash with getblockhash first.

Supported networks

• Mainnet
• Testnet

See also

• getblockhash
• getblockheader
• getblockstats