eth_getTransactionByHash | BNB Chain

BNB API method that returns information about a transaction from its hash. It is used to retrieve information about a specific transaction by its hash. The method returns an object with details about the transaction, such as the sender, recipient, gas used, transaction value, and more.

👍

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

Parameters

• hash — the hash identifying a transaction

Response

• object — the transaction response object, or null if no transaction is found:
  • blockHash — the block hash. Identifies the block in which the transaction was included. This field is null for transactions that have not yet been included in a block.
  • blockNumber — the number of the block in which the transaction was included. This field is null for transactions that have not yet been included in a block.
  • from — the address of the sender who initiated the transaction.
  • gas — the units of gas included in the transaction by the sender.
  • gasPrice — the price of gas in Wei included in the transaction by the sender.
  • maxFeePerGas — the maximum amount the transaction's sender is willing to pay per unit of gas for the transaction to be executed.
  • maxPriorityFeePerGas — the maximum priority fee the transaction sender is willing to pay per gas unit.
  • hash — the hash that uniquely identifies the transaction.
  • input — the optional input data sent with the transaction., usually used to interact with smart contracts.
  • nonce — a counter identifying the transaction's number sent by the sender wallet; it essentially identifies how many transactions an account has made. It is used to ensure each transaction is executed only once.
  • to — the recipient's address of the transaction if it was a transaction to an address. For contract creation transactions, this field is null.
  • transactionIndex — the index of the transaction within the block. This field is null for transactions that have not yet been included in a block.
  • value — the value of the native token transferred along with the transaction in Wei.
  • type — the type of the transaction. 0 indicates a regular transfer; 2 indicates a contract creation or smart contract function call.
  • accessList — a list of authorized addresses and storage keys the transaction plans to interact with.
  • v — the recovery parameter in the Ethereum Signature Algorithm (ECDSA).
  • r — the first component of the signature in the Ethereum Signature Algorithm (ECDSA).
  • s — the second component of the signature in the Ethereum Signature Algorithm (ECDSA).

eth_getTransactionByHash code examples

const { Web3 } = require("web3");
const NODE_URL = "CHAINSTACK_NODE_URL";
const web3 = new Web3(NODE_URL);

async function getTransaction(transactionHash) {
 const transaction = await web3.eth.getTransaction(transactionHash)
 console.log(transaction)
}

getTransaction("0x4cdc1e231274ffd15a30384eab7f45c9e42cd5aaa79d874f1cd23c52dfabe4b8")

const ethers = require('ethers');
const NODE_URL = "CHAINSTACK_NODE_URL";
const provider = new ethers.JsonRpcProvider(NODE_URL);

const getTransaction = async (transactionHash) => {
    const transaction = await provider.send("eth_getTransactionByHash", [transactionHash]);
    console.log(transaction);
  };

getTransaction("0x4cdc1e231274ffd15a30384eab7f45c9e42cd5aaa79d874f1cd23c52dfabe4b8")

from web3 import Web3  
node_url = "CHAINSTACK_NODE_URL" 

web3 = Web3(Web3.HTTPProvider(node_url)) 
print(web3.eth.get_transaction("0x4cdc1e231274ffd15a30384eab7f45c9e42cd5aaa79d874f1cd23c52dfabe4b8")) 

Use case

One use case for eth_getTransactionByHash is to inspect a specific transaction and display information about it, such as the address sent, the block it was included in, and the number of transactions the sender sent so far (nonce). This information can be useful for monitoring and analyzing transactions.

Try the eth_getTransactionByHash RPC method yourself