Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation "List Transactions by Block Hash UTXOs" retrieves a list of transactions associated with the Unspent Transaction Outputs (UTXOs) for a specific blockchain block identified by its hash. It is useful in scenarios where you want to analyze or audit all transactions that are unspent outputs within a particular block on a blockchain network.

Practical examples include:

  • Tracking all UTXOs in a given block to understand transaction flow.
  • Auditing blockchain activity for compliance or forensic analysis.
  • Building wallet or explorer features that display detailed transaction data per block.

Properties

Name Meaning
blockchain The blockchain network to query, e.g., Bitcoin, Ethereum, etc.
network The specific network environment, such as mainnet, testnet, or other supported networks.
blockHash The unique hash identifier of the block whose UTXO transactions you want to list.
context Optional context string to correlate or label the request (for tracking or logging).
limit Optional number to limit the maximum number of transactions returned.
offset Optional number to skip a certain number of transactions before starting to return data.

Output

The output is a JSON array where each element represents a transaction related to the UTXOs of the specified block hash. Each transaction object contains details as provided by the Crypto APIs service, typically including transaction identifiers, inputs, outputs, amounts, and status.

If binary data were involved (not indicated here), it would represent raw transaction data or related files, but this operation focuses on JSON transaction data only.

Dependencies

  • Requires an active connection to the Crypto APIs REST API.
  • Needs a valid API authentication token configured in n8n credentials to authorize requests.
  • The node reads from a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to map operations and parameters.

Troubleshooting

  • Operation Not Found Error: If the specified operation cannot be found, ensure the operation name matches exactly and the bundled OpenAPI spec file is present and correctly loaded.
  • Invalid Parameters: Missing or incorrect blockchain, network, or blockHash parameters will cause API errors. Verify these values are correct and correspond to supported blockchains/networks.
  • API Authentication Errors: Ensure the API key credential is properly set up in n8n and has sufficient permissions.
  • Rate Limits or Quotas: The external API may enforce rate limits; if exceeded, requests may fail temporarily.
  • Empty Results: If no transactions are returned, verify the block hash exists and contains UTXO transactions.

Links and References

Discussion