READ-ONLY EXAMPLE / getblockchaininfo
{
"jsonrpc": "1.0",
"id": "example",
"method": "getblockchaininfo",
"params": []
}Start with a precise question
Inspecting one output, reading a known transaction, and building a tracked-wallet overview require different coverage. Name the feature narrowly and choose your source around the exact records it needs.
A focused method map
| Question | Method | Keep in mind |
|---|---|---|
| What does this node report about its chain? | getblockchaininfo | Use node context, not invented live status. |
| Is this output returned as unspent? | gettxout | Identify the transaction and output index. |
| Which outputs does a configured wallet list? | listunspent | Wallet scope is not arbitrary address discovery. |
Preserve the outpoint
Use the network, transaction identifier, and output index as explicit fields. Keep the amount and observation time separate from payment acceptance policy. Do not turn an empty result or failed request into an unsupported explanation about an entire wallet.
For gettxout, the documented mempool option affects the view used by the query. Check the reference before interpreting an absent output.
Primary reference: Bitcoin gettxout reference. Check the upstream documentation for current method and integration details.
Build a better mental model
Read the Bitcoin API and UTXO guide, then use the provider evaluation process to test actual data coverage.