eth_getSystemTxsByBlockNumber
JSON-RPC method returns system transactions for a given block number on Hyperliquid EVM. This Hyperliquid-specific method provides access to internal system transactions that handle protocol operations, network maintenance, and other system-level activities.
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 number - The block number to retrieve system transactions from
Parameter details
blockNumber
(string, required) — Block identifier:"latest"
,"earliest"
,"pending"
, or a specific block number in hexadecimal
Response
The method returns an array of system transaction objects for the specified block.Response structure
System transactions array:- Array of system transaction objects
- Empty array if no system transactions exist in the block
- Each transaction contains system-specific information
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
System transaction types:- System transactions have special type identifiers
- Different types handle various protocol operations
- Types may include validator operations, protocol updates, or network maintenance
- System transactions often have zero gas price
Usage example
Basic implementation
HyperCore system transactions
System transaction characteristics
Origin and purpose:- System transactions originate from HyperCore
- Handle protocol operations and network maintenance
- Often have zero gas price (system-funded)
- Different transaction types for different operations
Sequential block analysis
Block-by-block monitoring:- Use block numbers for sequential analysis
- Track system transaction patterns over time
- Monitor protocol operations and network health
- Analyze system transaction frequency and types
Example request
Shell
Use cases
Theeth_getSystemTxsByBlockNumber
method is essential for applications that need to:
- Protocol monitoring: Monitor HyperCore system operations and protocol activities
- Network analysis: Analyze network health and system transaction patterns
- Block explorers: Display comprehensive block information including system transactions
- Analytics platforms: Study protocol behavior and system operation trends
- Development tools: Debug and understand system-level blockchain operations
- Sequential analysis: Track system transactions across block ranges
- Audit systems: Verify system operations and protocol compliance
- Integration services: Provide system transaction data to external applications
System transactions are internal protocol operations that may not appear in regular transaction lists. They provide insight into network maintenance, protocol operations, and system-level activities on Hyperliquid EVM.
Body
application/json
JSON-RPC version
Available options:
2.0
The RPC method name
Available options:
eth_getSystemTxsByBlockNumber
Parameters: [blockNumber]
Request identifier