The eth_getTransactionByHash method returns comprehensive information about a transaction identified by its unique hash. This is one of the most commonly used methods for retrieving transaction details directly.

Use Cases

Transaction status confirmation
Transaction validation
Payment verification
Smart contract interaction analysis
Transaction monitoring
Gas usage analysis
Historical transaction data retrieval
Transaction debugging

Method Details

This method retrieves detailed transaction data using the transaction's unique hash.

Parameters:

hashstring[required]

The hash of the transaction

Returns:

resultobject

The transaction object, or null if not found

blockHashstring

Hash of the block containing this transaction, null for pending transactions

blockNumberstring

Block number containing this transaction (hex), null for pending transactions

fromstring

Address of the sender

gasstring

Gas provided by the sender (hex)

gasPricestring

Gas price in wei (hex)

maxFeePerGasstring

Maximum fee per gas (EIP-1559 transactions)

maxPriorityFeePerGasstring

Maximum priority fee per gas (EIP-1559 transactions)

hashstring

Transaction hash

inputstring

Transaction data payload

noncestring

Number of transactions from sender prior to this one (hex)

tostring

Recipient address, null for contract creation transactions

transactionIndexstring

Integer of the transaction's position in the block (hex), null for pending transactions

valuestring

Value transferred in wei (hex)

typestring

Transaction type (0=legacy, 1=EIP2930, 2=EIP1559)

accessListarray

List of addresses and storage keys (EIP-2930 and EIP-1559)

chainIdstring

Chain ID specified in the transaction

vstring

V parameter of the signature

rstring

R parameter of the signature

sstring

S parameter of the signature

Response Example

{
	"jsonrpc": "2.0",
	"id": 1,
	"result": {
		"blockHash": "0xb3b20624f8f0f86eb50dd04688409e5cea4bd02d700bf6e79e9384d47d6a5a35",
		"blockNumber": "0x11a48cb",
		"from": "0x28c6c06298d514db089934071355e5743bf21d60",
		"gas": "0x21924",
		"gasPrice": "0x1057b28df",
		"maxFeePerGas": "0x11986c07a",
		"maxPriorityFeePerGas": "0x77359400",
		"hash": "0x5d15326cb350e13d19d1618b7534dcad9feac5cce8a877b8e6fdfd963a4889f7",
		"input": "0xa9059cbb000000000000000000000000ae2fc483527b8ef99eb5d9b44875f005ba1fae9600000000000000000000000000000000000000000000001158e460913d00000",
		"nonce": "0x3b50",
		"to": "0xdac17f958d2ee523a2206206994597c13d831ec7",
		"transactionIndex": "0x4d",
		"value": "0x0",
		"type": "0x2",
		"accessList": [],
		"chainId": "0x1",
		"v": "0x0",
		"r": "0x35707b530856150cec9ef609a724e2eb651f71ed9f0b0f94d9969919dae58387",
		"s": "0x7b305ef8f21e889f63d5178e7d2cbb85880ceaae045b0f46aef808c70b3a7a42"
	}
}

Identifying Transaction Types

By examining the transaction data, you can identify common transaction patterns:

Simple ETH Transfer:

to is a regular address (not a contract)
input is "0x" (empty data)
value is greater than 0

ERC-20 Token Transfer:

to is a token contract address
input starts with "0xa9059cbb" (transfer method signature)
value is typically 0

Contract Deployment:

to is null
input contains contract bytecode

Contract Method Call:

to is a contract address
input starts with function signature (first 4 bytes of keccak256 hash of function name and parameters)
May include value if the function is payable


### See also

- <Link to="/docs/ethereum/core-methods/eth_getTransactionReceipt" title="Check transaction execution status">eth_getTransactionReceipt</Link> - Get transaction receipt with execution results and events
- <Link to="/docs/ethereum/core-methods/eth_getTransactionByBlockHashAndIndex" title="Find transactions by position in a block">eth_getTransactionByBlockHashAndIndex</Link> - Look up transactions using a block hash and index position

Help Us Get Better!

Share this page and help us create an even better product for you.

eth_getTransactionByBlockNumberAndIndex

eth_getTransactionCount