Crypto APIs

Overview

This node operation fetches detailed information about internal transactions related to a specific Ethereum Virtual Machine (EVM) transaction hash on a chosen blockchain network. Internal transactions represent value transfers or contract calls that occur within a main transaction but are not recorded as separate transactions on the blockchain. This node is useful for developers, analysts, or auditors who want to inspect the granular details of what happened inside a particular EVM transaction.

Common scenarios:

• Auditing smart contract interactions by examining all internal calls triggered by a transaction.
• Tracking token movements or value transfers that happen internally during contract execution.
• Debugging complex transactions by understanding their internal flow and side effects.

Practical example:
You have a transaction hash from an Ethereum-based blockchain and want to list all internal operations (like contract calls or token transfers) that occurred inside it. By providing the blockchain name, network, and transaction hash, this node returns detailed internal transaction data, enabling deeper insight into the transaction's behavior.

Properties

Output

The output is a JSON array where each element represents an internal transaction detail associated with the specified transaction hash. Each item typically includes fields such as:

• Addresses involved (from, to)
• Value transferred
• Gas used
• Input data
• Call type or operation type
• Status or result of the internal call

If binary data is present (not typical for this operation), it would represent raw transaction or contract call data.

Dependencies

• Requires an active connection to the Crypto APIs REST API service.
• Needs an API key credential configured in n8n to authenticate requests.
• The node reads a local OpenAPI specification file (2024-12-12-final.json) bundled with the node for operation metadata but does not require user interaction with it.

Troubleshooting

• Common issues:

  • Invalid or missing transaction hash: Ensure the transaction hash is correct and corresponds to the selected blockchain and network.
  • Network mismatch: Using a transaction hash from one network (e.g., testnet) while specifying another network (e.g., mainnet) will cause no results or errors.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.

• Error messages:

  • Operation <operationName> not found: Indicates the requested operation is not recognized; usually a configuration or version mismatch.
  • API request failures may return error messages from the external service, such as rate limits exceeded or invalid parameters. Check credentials and input values.

• To resolve errors, verify all required properties are provided, check API credentials, and confirm network/blockchain correctness.

Links and References

• Crypto APIs Documentation
• Ethereum Transaction Concepts
• Understanding Internal Transactions