Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation "List Transactions by Block Height EVM" under the "blocks" resource interacts with a blockchain API to retrieve a list of transactions included in a specific Ethereum Virtual Machine (EVM) compatible blockchain block identified by its height. It is useful for users who want to analyze or monitor all transactions that occurred at a particular block height on supported EVM blockchains.

Practical examples include:

  • Auditing all transactions in a given block for compliance or forensic analysis.
  • Building dashboards that display transaction activity per block.
  • Triggering workflows based on transactions confirmed at a certain block height.

Properties

Name Meaning
blockchain The target blockchain network (e.g., Ethereum, Binance Smart Chain)
network The specific network environment within the blockchain (e.g., mainnet, testnet)
blockHeight The numeric height of the block from which to list transactions
context Optional string to correlate or tag the request context
limit Optional number to limit how many transactions to return
offset Optional number to specify the starting point for pagination of returned transactions

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 underlying blockchain API, such as transaction hash, sender and receiver addresses, value transferred, gas used, and other relevant blockchain transaction data.

If binary data were involved (e.g., raw transaction payloads), it would be summarized accordingly, but this operation focuses on JSON transaction details.

Dependencies

  • Requires an API key credential for accessing the Crypto APIs REST API.
  • The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node to dynamically resolve API paths and parameters.
  • Network connectivity to the Crypto APIs service endpoint.
  • Proper configuration of the API authentication credential in n8n.

Troubleshooting

  • Operation Not Found Error: If the specified operation cannot be found in the API spec, ensure the operation name matches exactly and the bundled API spec file is present and uncorrupted.
  • Invalid Parameter Errors: Providing invalid or missing required parameters like blockchain, network, or blockHeight will cause errors. Double-check parameter values and types.
  • API Authentication Failures: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Rate Limiting or Quota Exceeded: The external API may throttle requests; consider adding delays or handling retries.
  • Empty Results: If no transactions are returned, verify the block height exists and contains transactions on the selected blockchain and network.

Links and References

Discussion