> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.
## Submitting Feedback
If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:
POST https://docs.chainstack.com/feedback
```json
{
"path": "/reference/hyperliquid-evm-eth-get-transaction-by-block-hash-and-index",
"feedback": "Description of the issue"
}
```
Only submit feedback when you have something specific and actionable to report.
# eth_getTransactionByBlockHashAndIndex | Hyperliquid EVM
> Returns transaction information by block hash and transaction index.
This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
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 today**
[Start for free](https://console.chainstack.com/) 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 Shell theme={"system"}
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.
## OpenAPI
````yaml /openapi/hyperliquid_node_api/evm_eth_get_transaction_by_block_hash_and_index.json post /evm
openapi: 3.0.0
info:
title: Hyperliquid EVM API - eth_getTransactionByBlockHashAndIndex
version: 1.0.0
servers:
- url: >-
https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274
security: []
paths:
/evm:
post:
summary: eth_getTransactionByBlockHashAndIndex
description: Returns transaction information by block hash and transaction index.
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- jsonrpc
- method
- params
- id
properties:
jsonrpc:
type: string
enum:
- '2.0'
default: '2.0'
description: JSON-RPC version
method:
type: string
enum:
- eth_getTransactionByBlockHashAndIndex
default: eth_getTransactionByBlockHashAndIndex
description: The RPC method name
params:
type: array
description: 'Parameters: [blockHash, transactionIndex]'
default:
- >-
0x53e84f299e6893680383c6a53329574122a7292e5bb9397bb6a0b51b4db5957a
- '0x0'
id:
type: integer
default: 1
description: Request identifier
example:
jsonrpc: '2.0'
method: eth_getTransactionByBlockHashAndIndex
params:
- >-
0x53e84f299e6893680383c6a53329574122a7292e5bb9397bb6a0b51b4db5957a
- '0x0'
id: 1
responses:
'200':
description: Successful response with transaction information
content:
application/json:
schema:
type: object
properties:
jsonrpc:
type: string
description: JSON-RPC version
id:
type: integer
description: Request identifier
result:
type: object
properties:
hash:
type: string
description: Transaction hash
nonce:
type: string
description: Transaction nonce
blockHash:
type: string
description: Hash of the block containing the transaction
blockNumber:
type: string
description: Number of the block containing the transaction
transactionIndex:
type: string
description: Index of the transaction in the block
from:
type: string
description: Address of the sender
to:
type: string
description: Address of the receiver
value:
type: string
description: Value transferred in wei
gas:
type: string
description: Gas limit provided by the sender
gasPrice:
type: string
description: Gas price provided by the sender in wei
input:
type: string
description: Data sent along with the transaction
v:
type: string
description: ECDSA recovery id
r:
type: string
description: ECDSA signature r
s:
type: string
description: ECDSA signature s
type:
type: string
description: Transaction type
example:
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'
````