Crypto APIs icon

Crypto APIs

Interact with Crypto APIs REST API

Actions113

Overview

This node operation decodes a raw Ethereum Virtual Machine (EVM) transaction hex string into a structured JSON representation. It is useful for developers, blockchain analysts, or anyone working with raw blockchain transaction data who needs to interpret or inspect the contents of a raw transaction before broadcasting or analyzing it.

Typical use cases include:

  • Debugging or verifying raw transactions before sending them to the network.
  • Extracting detailed transaction information such as sender, recipient, value, gas, and input data from raw hex.
  • Integrating with blockchain tools that require decoded transaction details for further processing or display.

For example, a user might input a raw transaction hex string from an Ethereum wallet or a smart contract interaction and get back a parsed JSON object describing all transaction fields in human-readable form.

Properties

Name Meaning
blockchain The blockchain network to decode the transaction on (e.g., Ethereum, Binance Smart Chain).
network The specific network within the blockchain (e.g., mainnet, testnet).
context Optional context string to correlate requests/responses, useful for tracking.
JSON Body A collection of additional parameters:
- rawTransactionHex The raw transaction hex string representing the encoded EVM transaction to decode.

Output

The output is a JSON array where each item contains the decoded transaction details corresponding to the input raw transaction hex. The structure typically includes fields such as:

  • nonce: Transaction count of the sender.
  • gasPrice / maxFeePerGas / maxPriorityFeePerGas: Gas pricing details.
  • gasLimit: Maximum gas allowed for the transaction.
  • to: Recipient address.
  • value: Amount of cryptocurrency transferred.
  • data: Input data or payload of the transaction.
  • v, r, s: Signature components.
  • Other relevant EVM transaction fields depending on the blockchain and network.

If the node supports binary data output, it would represent raw transaction bytes or related binary artifacts, but this node focuses on JSON decoding output.

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 rely on it at runtime beyond static definitions.

Troubleshooting

  • Operation Not Found Error: If the specified operation is not found, ensure the "Decode Raw Transaction Hex EVM" operation is correctly selected and the node version matches the bundled API spec.
  • Invalid Raw Transaction Hex: Providing malformed or incomplete raw transaction hex strings will cause decoding failures. Verify the hex string format and completeness.
  • API Authentication Errors: Ensure the API key credential is valid and has permissions for blockchain utilities.
  • Network or Blockchain Mismatch: Using unsupported or incorrect blockchain/network combinations may result in errors or empty responses. Confirm supported values.
  • Continue On Fail Behavior: If enabled, errors will be returned as JSON objects with an error field instead of stopping execution.

Links and References

Discussion