Ethereum

Overview

This node interacts with the Ethereum blockchain, specifically focusing on transactions when using the "Transaction" resource. The "Get Transaction" operation retrieves detailed information about a specific Ethereum transaction by its hash.

Common scenarios where this node is beneficial include:

• Verifying the status and details of a transaction after sending ETH or tokens.
• Auditing or tracking transactions for accounting or compliance purposes.
• Fetching transaction metadata such as sender, recipient, value, gas price, and nonce for further processing or display.

Practical example:

• After sending ETH via another operation, you can use this node to fetch the transaction details by providing the transaction hash, confirming that the transaction was successfully broadcast and mined.

Properties

Output

The output JSON object contains detailed information about the requested Ethereum transaction:

• hash: The transaction hash.
• from: The address that sent the transaction.
• to: The recipient address of the transaction.
• value: The amount of ETH transferred, formatted in Ether units.
• gasPrice: The gas price used for the transaction, represented as a string.
• gasLimit: The gas limit set for the transaction, represented as a string.
• nonce: The transaction count of the sender before this transaction.
• data: Any additional data payload included in the transaction.

If the transaction is not found, the node throws an error indicating so.

Dependencies

• Requires access to an Ethereum RPC endpoint URL (can be a public node or a private provider).
• No explicit API keys are required unless connecting to a private or authenticated Ethereum node.
• Uses the ethers library internally to interact with the Ethereum blockchain.

Troubleshooting

• Error: "Transaction not found"
  This occurs if the provided transaction hash does not exist or is not yet indexed by the connected Ethereum node. Verify the hash is correct and that the RPC URL points to a fully synced node.

• Connection issues to RPC URL
  If the node cannot connect to the specified RPC URL, ensure the URL is valid, reachable, and supports the Ethereum network you intend to query.

• Empty or invalid transaction hash input
  Make sure the "Transaction Hash" property is correctly filled with a valid Ethereum transaction hash string.

Links and References

• Ethereum JSON-RPC API
• ethers.js Documentation
• Understanding Ethereum Transactions