eth_getSystemTxsByBlockHash
JSON-RPC method returns system transactions for a given block hash on Hyperliquid EVM. This Hyperliquid-specific method provides access to internal system transactions using the block’s unique hash identifier, ensuring precise block identification even during chain reorganizations.
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 one parameter:- Block hash - The hash of the block to retrieve system transactions from
Parameter details
blockHash
(string, required) — The 32-byte hash of the block
Response
The method returns an array of system transaction objects for the specified block, ornull
if the block is not found.
Response structure
System transactions array:- Array of system transaction objects
- Empty array if no system transactions exist in the block
null
if the block hash doesn’t exist
hash
— System transaction hashtype
— System transaction type identifierblockNumber
— Block number containing the system transactionblockHash
— Hash of the block containing the system transactiontransactionIndex
— Index of the system transaction in the blockfrom
— System address that initiated the transactionto
— Target address of the system transactionvalue
— Value transferred in the system transactiongasUsed
— Gas used by the system transactiongasPrice
— Gas price for the system transaction (often 0 for system txs)input
— Input data for the system transactionstatus
— System transaction status (0x0 for failure, 0x1 for success)
Data interpretation
Hash-based identification:- 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
Usage example
Basic implementation
Hash-based identification benefits
Immutable block references
Precise identification:- Block hashes provide cryptographically unique identifiers
- Remain constant even during chain reorganizations
- Enable precise block version identification
- Useful for audit trails and data consistency
Chain reorganization handling
Robust data retrieval:- Hash-based queries work even during chain reorganizations
- Provides access to specific block versions
- Maintains data integrity across different chain states
- Essential for forensic analysis and debugging
Example request
Shell
Use cases
Theeth_getSystemTxsByBlockHash
method is essential for applications that need to:
- Precise block identification: Access system transactions from specific block versions using immutable hashes
- Chain reorganization handling: Maintain data consistency during blockchain reorganizations
- Audit systems: Create immutable audit trails using cryptographic block identifiers
- Block explorers: Provide precise block navigation and system transaction display
- Analytics platforms: Analyze system transactions with consistent block references
- Development tools: Debug system operations using specific block versions
- Protocol monitoring: Monitor HyperCore system operations with precise identification
- Integration services: Provide system transaction data with immutable identifiers
Block hashes provide immutable identification and are essential for maintaining data consistency during chain reorganizations. If a block hash is not found, it may indicate the block was reorganized out of the canonical chain.
Body
application/json