Crypto APIs

Overview

This node operation "List Transactions by Block Hash EVM" allows users to retrieve a list of transactions included in a specific Ethereum Virtual Machine (EVM) compatible blockchain block, identified by its block hash. It is useful for blockchain analysts, developers, or applications that need to inspect or process all transactions within a particular block on an EVM chain.

Practical examples include:

• Auditing all transactions in a given block for compliance or forensic analysis.
• Building dashboards or explorers that display transaction details per block.
• Triggering workflows based on the presence or content of transactions in a specific block.

Properties

Output

The output is a JSON array where each element represents a transaction included in the specified block. Each transaction object contains detailed information as provided by the Crypto APIs service, such as transaction hashes, sender and receiver addresses, amounts, gas fees, and other relevant blockchain transaction data.

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

Dependencies

• Requires an API key credential for the Crypto APIs REST API.
• The node reads from a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically configure endpoints and parameters.
• Network connectivity to the Crypto APIs service endpoint is necessary.
• No additional external dependencies beyond standard n8n workflow and node modules.

Troubleshooting

• Operation Not Found Error: If the specified operation cannot be found, ensure the operation name matches exactly and that the bundled OpenAPI spec file is present and correctly loaded.
• Invalid or Missing Parameters: Required parameters like blockchain, network, and blockHash must be provided; missing these will cause errors.
• API Authentication Errors: Ensure the API key credential is configured properly in n8n and has sufficient permissions.
• Rate Limits or Quotas: The Crypto APIs service may enforce rate limits; hitting these will result in errors—consider adding retry logic or increasing limits if possible.
• Empty Results: If no transactions are returned, verify the block hash is correct and corresponds to a block containing transactions.

Links and References

• Crypto APIs Documentation
• Ethereum Block and Transaction Concepts
• EVM Compatible Chains Overview