POST
/
evm
eth_getTransactionByBlockHashAndIndex
curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm \
  --header 'Content-Type: application/json' \
  --data '{
  "jsonrpc": "2.0",
  "method": "eth_getTransactionByBlockHashAndIndex",
  "params": [
    "0x53e84f299e6893680383c6a53329574122a7292e5bb9397bb6a0b51b4db5957a",
    "0x0"
  ],
  "id": 1
}'
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "hash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
    "nonce": "0x1",
    "blockHash": "0x53e84f299e6893680383c6a53329574122a7292e5bb9397bb6a0b51b4db5957a",
    "blockNumber": "0x9d0c37",
    "transactionIndex": "0x0",
    "from": "0xFC1286EeddF81d6955eDAd5C8D99B8Aa32F3D2AA",
    "to": "0x5555555555555555555555555555555555555555",
    "value": "0xde0b6b3a7640000",
    "gas": "0x5208",
    "gasPrice": "0x3b9aca00",
    "input": "0x",
    "v": "0x1c",
    "r": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
    "s": "0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890",
    "type": "0x0"
  }
}
The eth_getTransactionByBlockHashAndIndex JSON-RPC method returns transaction information by block hash and transaction index. This method is useful for retrieving specific transactions when you know the block hash and the transaction’s position within that block.
Get your own node endpoint todayStart 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

The method takes two parameters:
  1. Block hash - The hash of the block containing the transaction
  2. Transaction index - The index position of the transaction within the block

​
Parameter details

  • blockHash (string, required) — The 32-byte hash of the block containing the transaction
  • transactionIndex (string, required) — The index position of the transaction in the block as a hexadecimal string (0-based)

​
Response

The method returns detailed transaction information, or null if the transaction is not found.

​
Response structure

Transaction object:
  • hash — The 32-byte transaction hash
  • nonce — Transaction nonce (number of transactions sent by sender)
  • blockHash — Hash of the block containing the transaction
  • blockNumber — Number of the block containing the transaction
  • transactionIndex — Index of the transaction in the block
  • from — Address of the transaction sender
  • to — Address of the transaction receiver (null for contract creation)
  • value — Value transferred in wei as a hexadecimal string
  • gas — Gas limit provided by the sender
  • gasPrice — Gas price provided by the sender in wei
  • input — Data sent along with the transaction
  • v, r, s — ECDSA signature components
  • type — Transaction type (0x0 for legacy, 0x1 for EIP-2930, 0x2 for EIP-1559)

​
Transaction types

Legacy transactions (type 0x0):
  • Traditional Ethereum transactions
  • Use gasPrice for fee calculation
  • Simple fee structure
EIP-2930 transactions (type 0x1):
  • Include access lists for gas optimization
  • Still use gasPrice for fees
  • Reduce gas costs for certain operations
EIP-1559 transactions (type 0x2):
  • Use maxFeePerGas and maxPriorityFeePerGas
  • Dynamic fee structure with base fee
  • More predictable fee estimation

​
Hash-based transaction retrieval

​
Precise block identification

Immutable block references:
  • Block hashes provide unique, immutable block identification
  • Useful during chain reorganizations when block numbers may change
  • Ensures retrieval from specific block versions
  • Maintains data consistency across different chain states

​
Index-based access

Sequential processing:
  • Process transactions in block order using indices (0-based)
  • Iterate through all transactions in a block systematically
  • Maintain transaction execution order for analysis
  • Access specific transactions when index is known

​
Example request

Shell
curl -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0","method": "eth_getTransactionByBlockHashAndIndex","params": ["0x53e84f299e6893680383c6a53329574122a7292e5bb9397bb6a0b51b4db5957a","0x0"],"id": 1}' \
  https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm

​
Use cases

The eth_getTransactionByBlockHashAndIndex method is essential for applications that need to:
  • Block transaction processing: Process all transactions in a specific block sequentially
  • Transaction ordering analysis: Analyze transaction execution order within blocks
  • Block explorers: Display transactions in block context with proper indexing
  • Analytics platforms: Collect transaction data for comprehensive analysis
  • Audit systems: Verify transaction ordering and block composition
  • Development tools: Debug and analyze transaction execution within blocks
  • Historical analysis: Study transaction patterns in historical blocks using immutable block hashes
  • Integration services: Provide transaction data to external systems with precise block identification
Transaction indices are 0-based and sequential within each block. If the specified index exceeds the number of transactions in the block, the method returns null. Block hashes provide immutable identification, useful during chain reorganizations.

Body

application/json
​
jsonrpc
enum<string>
default:2.0
required

JSON-RPC version

Available options:
2.0
​
method
enum<string>
default:eth_getTransactionByBlockHashAndIndex
required

The RPC method name

Available options:
eth_getTransactionByBlockHashAndIndex
​
params
any[]
required

Parameters: [blockHash, transactionIndex]

​
id
integer
default:1
required

Request identifier

Response

200 - application/json

Successful response with transaction information

​
jsonrpc
string

JSON-RPC version

​
id
integer

Request identifier

​
result
object