EVM icon

EVM

Interact with an EVM chain
Join our community

Actions11

Overview

The node interacts with Ethereum Virtual Machine (EVM) compatible blockchains to perform various blockchain-related operations. Specifically, the Get Transaction Details operation retrieves detailed information about a specific blockchain transaction given its transaction hash. This includes decoding events emitted by the transaction and providing comprehensive data beyond just the receipt.

This operation is useful when you want to audit or analyze a particular transaction on an EVM chain, such as Ethereum, Binance Smart Chain, Polygon, etc. For example, you might use it to:

  • Verify the outcome and details of a token transfer.
  • Extract event logs for further processing.
  • Debug smart contract interactions by inspecting transaction internals.

Properties

Name Meaning
Transaction Hash The unique identifier (hash) of the transaction to retrieve details for. Example: 0x1234...

Output

The output JSON contains detailed information about the specified transaction, including but not limited to:

  • Transaction metadata (hash, block number, timestamp).
  • Sender and receiver addresses.
  • Value transferred.
  • Gas used and gas price details.
  • Decoded event logs emitted by the transaction.
  • Status and confirmations.

This rich detail allows users to fully understand what happened during the transaction execution.

The node does not output binary data for this operation.

Dependencies

  • Requires connection to an EVM-compatible blockchain node via an RPC URL.
  • Requires an API key credential that provides access to the blockchain node.
  • Uses the ethers library for blockchain interaction.
  • Utilizes helper modules for nonce management and utility functions bundled within the node.

Troubleshooting

  • Invalid Transaction Hash: If the provided transaction hash is malformed or does not exist on the connected network, the node may throw an error or return empty results. Ensure the hash is correct and corresponds to the selected blockchain.
  • RPC Connection Issues: Failure to connect to the blockchain node (due to incorrect RPC URL or network issues) will cause errors. Verify your RPC endpoint and network connectivity.
  • Credential Errors: Missing or invalid API credentials will prevent the node from querying the blockchain. Make sure the required API authentication token is configured properly.
  • Timeouts or Slow Responses: Blockchain nodes can sometimes respond slowly, especially for older or complex transactions. Consider increasing timeout settings if available or retrying later.

Links and References

Discussion