> ## 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.
# eth_getTransactionByBlockNumberAndIndex | Hyperliquid EVM
> The eth_getTransactionByBlockNumberAndIndex JSON-RPC method returns transaction information by block number 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_getTransactionByBlockNumberAndIndex` JSON-RPC method returns transaction information by block number and transaction index. This method is ideal for sequential transaction processing and building comprehensive blockchain datasets when working with block numbers.
**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 number** - The number of the block containing the transaction
2. **Transaction index** - The index position of the transaction within the block
### Parameter details
* `blockNumber` (string, required) — Block identifier: `"latest"`, `"earliest"`, `"pending"`, or a specific block number in hexadecimal
* `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)
### Block number formats
**Special identifiers:**
* `"latest"` — Most recent block's transactions
* `"earliest"` — Genesis block transactions (usually none)
* `"pending"` — Pending block transactions
**Hexadecimal numbers:**
* `"0x0"` — Genesis block
* `"0x9d0c37"` — Block 10,291,255 (decimal)
## Sequential processing
### Range-based analysis
**Block range processing:**
* Process transactions across multiple consecutive blocks
* Build comprehensive transaction datasets systematically
* Analyze transaction patterns over time periods
* Generate time-series transaction analytics
**Chronological analysis:**
* Process transactions in chronological order
* Track transaction evolution and patterns over time
* Build historical transaction databases
* Analyze network activity trends and cycles
### Efficient iteration
**Block-by-block processing:**
* Iterate through blocks sequentially using block numbers
* Process all transactions within each block systematically
* Maintain transaction order and block context
* Build complete blockchain transaction datasets
**Parallel processing:**
* Process multiple blocks concurrently for efficiency
* Distribute transaction processing across workers
* Optimize throughput for large-scale analysis
* Balance load across processing resources
## Development patterns
### Systematic data collection
**Complete blockchain analysis:**
* Process all transactions from genesis to latest block
* Build comprehensive transaction databases
* Generate complete network activity statistics
* Create historical blockchain datasets
**Incremental processing:**
* Process new blocks as they are mined
* Maintain up-to-date transaction datasets
* Implement efficient incremental updates
* Handle real-time transaction processing
### Transaction indexing
**Index-based retrieval:**
* Build transaction indexes based on block position
* Enable efficient transaction lookup by position
* Maintain transaction ordering within blocks
* Optimize for sequential access patterns
**Batch processing:**
* Process multiple transactions from the same block
* Optimize API usage and network efficiency
* Implement efficient batch processing workflows
* Reduce overhead for bulk operations
## Integration strategies
### Analytics platforms
**Time-series analysis:**
* Analyze transaction patterns over time using block numbers
* Build time-based transaction metrics and KPIs
* Generate historical transaction reports
* Create transaction trend analysis systems
**Network monitoring:**
* Monitor transaction activity in real-time using latest blocks
* Track network utilization and capacity metrics
* Generate network health indicators
* Build transaction-based alerting systems
### Block explorers
**Sequential navigation:**
* Enable navigation through blocks using block numbers
* Display transactions in chronological order
* Provide block-based transaction browsing
* Show transaction context within block sequences
**Historical exploration:**
* Browse historical transactions using block numbers
* Provide time-based transaction search capabilities
* Enable exploration of transaction history
* Show transaction evolution over time
## Example request
```shell Shell theme={"system"}
curl -X POST \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"eth_getTransactionByBlockNumberAndIndex","params":["0x9d0c37","0x0"],"id":1}' \
https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm
```
## Use cases
The `eth_getTransactionByBlockNumberAndIndex` method is essential for applications that need to:
* **Sequential processing**: Process transactions across block ranges systematically
* **Time-series analysis**: Analyze transaction patterns over time using block numbers
* **Blockchain synchronization**: Build and maintain synchronized blockchain datasets
* **Analytics platforms**: Collect comprehensive transaction data for analysis
* **Block explorers**: Display transactions in chronological block order
* **Historical analysis**: Study transaction evolution and network growth patterns
* **Data archival**: Archive transaction data with proper temporal context
* **Network monitoring**: Track transaction activity and network utilization over time
* **Research platforms**: Study blockchain behavior and transaction patterns
* **Audit systems**: Verify transaction sequences and blockchain integrity
* **Development tools**: Debug and test applications with historical transaction data
* **Compliance monitoring**: Track transactions for regulatory compliance over time
* **Performance analysis**: Analyze network performance and transaction throughput
* **Integration services**: Provide chronological transaction data to external systems
* **Educational platforms**: Demonstrate blockchain concepts using real transaction data
* **Forensic analysis**: Investigate transaction patterns and blockchain activities
* **Risk management**: Analyze transaction risks and patterns over time periods
* **Portfolio tracking**: Track user transactions across multiple blocks chronologically
* **DeFi analytics**: Analyze DeFi protocol activity and usage patterns over time
* **Market analysis**: Study trading activity and market behavior using transaction data
* **MEV research**: Analyze maximal extractable value patterns across blocks
* **Network economics**: Study transaction fees and network economics over time
* **Chain analysis**: Analyze blockchain structure and transaction relationships
* **Security monitoring**: Monitor suspicious activities across block ranges
* **Data visualization**: Create time-based charts and graphs of transaction activity
This method provides efficient sequential transaction access by block number, enabling comprehensive time-based analysis on the Hyperliquid EVM platform.
This method supports special block identifiers like `"latest"` and `"pending"`, making it suitable for both historical analysis and real-time transaction monitoring.
## OpenAPI
````yaml /openapi/hyperliquid_node_api/evm_eth_get_transaction_by_block_number_and_index.json post /evm
openapi: 3.0.0
info:
title: Hyperliquid EVM API - eth_getTransactionByBlockNumberAndIndex
version: 1.0.0
servers:
- url: >-
https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274
security: []
paths:
/evm:
post:
summary: eth_getTransactionByBlockNumberAndIndex
description: Returns transaction information by block number 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_getTransactionByBlockNumberAndIndex
default: eth_getTransactionByBlockNumberAndIndex
description: The RPC method name
params:
type: array
description: 'Parameters: [blockNumber, transactionIndex]'
default:
- '0x9d0c37'
- '0x0'
id:
type: integer
default: 1
description: Request identifier
example:
jsonrpc: '2.0'
method: eth_getTransactionByBlockNumberAndIndex
params:
- '0x9d0c37'
- '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: >-
0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890
blockNumber: '0x9d0c37'
transactionIndex: '0x0'
from: '0xFC1286EeddF81d6955eDAd5C8D99B8Aa32F3D2AA'
to: '0x5555555555555555555555555555555555555555'
value: '0xde0b6b3a7640000'
gas: '0x5208'
gasPrice: '0x3b9aca00'
input: 0x
v: '0x1c'
r: >-
0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef
s: >-
0xabcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890
type: '0x0'
````