Actions113
- blocks Actions
- Get Block Details By Block Hash UTXOs
- List Transactions by Block Hash EVM
- List Transactions by Block Hash UTXOs
- List Transactions By Block Hash XRP
- List Transactions By Block Height XRP
- List Transactions by Block Height EVM
- List Transactions by Block Height UTXOs
- Get Block Details By Block Height UTXOs
- Get Block Details By Block Height EVM
- Get Block Details By Block Height XRP
- Get Block Details By Block Hash EVM
- Get Block Details By Block Hash XRP
- Get Last Mined Block EVM
- Get Last Mined Block UTXOs
- Get Latest Mined Block XRP
- List Latest Mined Blocks UTXOs
- List Latest Mined Blocks EVM
- List Latest Mined Blocks XRP
- HD Wallets Actions
- Sync HD Wallet (xPub, yPub, zPub)
- Derive And Sync New Receiving Addresses UTXO
- Derive And Sync New Change Addresses UTXO
- Derive And Sync New Receiving Addresses EVM
- Derive And Sync New Receiving Addresses XRP
- List Synced Addresses UTXO
- List Synced Addresses EVM
- List Synced Addresses XRP
- List HD Wallet (xPub, yPub, zPub) Transactions UTXO
- List HD Wallet (xPub, yPub, zPub) Transactions EVM
- List HD Wallet (xPub, yPub, zPub) Transactions XRP
- List HD Wallet (xPub, yPub, zPub) UTXOs
- Prepare A UTXO-Based Transaction From HD Wallet (xPub, yPub, zPub)
- Prepare A Transaction From an Address in HD Wallet (xPub, yPub, zPub) EVM
- Get HD Wallet (xPub, yPub, zPub) Assets UTXO
- Get HD Wallet (xPub, yPub, zPub) Assets EVM
- Get HD Wallet (xPub, yPub, zPub) Assets XRP
- Get HD Wallet (xPub, yPub, zPub) Details UTXO
- Get HD Wallet (xPub, yPub, zPub) Details EVM
- Get HD Wallet (xPub, yPub, zPub) Details XRP
- List Synced HD Wallets (xPub, yPub, zPub)
- Activate HD Wallet (xPub, yPub, zPub)
- Delete Synced HD Wallet (xPub, yPub, zPub)
- address-latest Actions
- Utilities Actions
- simulate-transactions Actions
- addresses-latest Actions
- Get Address Balance Solana
- List Transactions By Address Solana
- Get Address Balance EVM
- Get Address Balance XRP
- Get Address Balance Kaspa
- List Confirmed Transactions By Address EVM
- List Transactions by Address XRP
- List Confirmed Transactions By Address UTXOs
- List Confirmed Transactions By Address Kaspa
- List Unconfirmed Transactions by Address UTXOs
- List Internal Transactions By Address EVM
- Get Next Available Nonce EVM
- List Confirmed Tokens Transfers By Address EVM
- addresses-historical Actions
- Get Address Balance UTXOs
- List Confirmed Transactions By Address EVM history
- List Confirmed Transactions By Address UTXO Historical
- List Unspent Transaction Outputs By Address UTXOs
- Sync Address
- List Synced Addresses
- Get Synced Address Tokens Transfer EVM
- Activate Synced Address
- Delete Synced Address
- List Synced Address Internal Transactions EVM
- List Tokens By Address Synced EVM
- blockchain-events Actions
- New Confirmed Coins Transactions
- New Unconfirmed Coins Transactions
- New Confirmed Tokens Transactions
- New Confirmed Coins Transactions And Each Confirmation
- New Confirmed Tokens Transactions And Each Confirmation
- Mined Transaction
- New Block
- List Blockchain Events Subscriptions
- Get Blockchain Event Subscription Details By Reference ID
- Delete Blockchain Event Subscription
- Activate Blockchain Event Subscription
- New Confirmed Internal Transactions
- New Confirmed Internal Transactions And Each Confirmation
- Crypto Transactions Actions
- Get Transaction Details By Transaction Hash Solana
- Get Transaction Details By Transaction Id Kaspa
- Get Transaction Details By Transaction Hash EVM
- Get Transaction Details By Transaction Hash UTXOs
- Get Transaction Details By Transaction Hash XRP
- List Internal Transaction Details by Transaction Hash EVM
- List Tokens Transfers By Transaction Hash EVM
- List Logs By Transaction Hash EVM
- Get Raw Transaction Data UTXOs
- contracts Actions
- blockchain-fees Actions
- broadcast-transactions Actions
- prepare-transactions Actions
- Market Data & Prices Actions
Overview
This node operation fetches detailed information about a specific blockchain block by its hash on an EVM-compatible blockchain network. It is useful for users who want to retrieve comprehensive data about a particular block, such as its transactions, timestamp, miner, and other metadata, by providing the unique block hash.
Practical examples include:
- Monitoring a specific block for auditing or tracking purposes.
- Fetching block details to analyze transaction confirmations.
- Integrating block data into dashboards or reporting tools.
Properties
| Name | Meaning |
|---|---|
| blockchain | The blockchain network to query (e.g., Ethereum, Binance Smart Chain). |
| network | The specific network within the blockchain (e.g., mainnet, testnet). |
| blockHash | The unique hash identifier of the block whose details are to be retrieved. |
| context | Optional additional context string that can be used to correlate requests or responses. |
Output
The output is a JSON array where each item contains detailed information about the requested block. This typically includes fields such as block number, timestamp, list of transactions, miner address, gas used, and other relevant block metadata.
If the node supports binary data output, it would represent any associated binary content related to the block, but this operation primarily returns structured JSON data.
Dependencies
- Requires an API key credential for accessing the Crypto APIs REST API.
- The node depends on the Crypto APIs service to fetch blockchain data.
- No additional environment variables are explicitly required beyond the API authentication setup in n8n.
Troubleshooting
Common issues:
- Invalid or missing block hash: Ensure the block hash provided is correct and corresponds to the specified blockchain and network.
- Network or blockchain mismatch: Verify that the blockchain and network parameters match the block hash's origin.
- API authentication errors: Confirm that the API key credential is correctly configured and has sufficient permissions.
Error messages:
Operation <operationName> not found: Indicates an internal misconfiguration or unsupported operation; ensure the node version matches the API specification.- API request failures: Usually due to invalid parameters or connectivity issues; check parameter values and network access.