/hypercore JSON-RPC methods requires a Build plan or higher. View pricing to upgrade. For complete stream type definitions and filtering options, see the datasets documentation.The top-level height field was added to Hyperliquid's raw replica_cmds data on 2026-07-25, starting at block 1085381001. Blocks produced before that change are still returned in full, with abci_block and resps, but the response object has no height key, so the payload itself does not tell you which block you received. Track the block number from your own request when you query that range. This applies only to the replica_cmds stream. Every other stream returns block_number on every block.
Parameters
The stream type to query (trades, orders, events, book, twap, writer_actions, replica_cmds). The replica_cmds stream returns the raw HyperCore block, which has a different response shape than the other streams.
The specific block number to retrieve
Returns
The requested block object
Returned for the trades, orders, book, twap, events, and writer_actions streams.
Block number on the Hyperliquid chain
Block timestamp in ISO 8601 format
Local server timestamp in ISO 8601 format
List of events in this block; each event is a 2-item tuple of [address, payload]
Event address as a 0x-prefixed hex string
Event payload data
Builder address as a 0x-prefixed hex string (only present for some events)
Builder fee amount as a stringified number (only present for some events)
Client order identifier (only present for some events)
Realized PnL from this event as a stringified number
Instrument symbol (e.g., BTC, xyz:XYZ100, xyz:HOOD)
Whether the order crossed the book
Action direction describing the position change (e.g., Open Long, Open Short, Close Long, Close Short, Short > Long, Long > Short)
Fee amount as a stringified number (can be negative depending on rebates)
Token symbol used for fees (e.g., USDC)
Transaction hash as a 0x-prefixed hex string
Order identifier
Execution price as a stringified number
Trade side indicator (e.g., B or A)
Position size before the event as a stringified number
Execution size/quantity as a stringified number
Trade identifier
Event timestamp in milliseconds since Unix epoch
TWAP identifier if the event is associated with a TWAP; null if not associated with a TWAP
Returned for the replica_cmds stream, which carries the raw HyperCore block. See the blocks dataset for the full field reference and the complete list of action types.
Top-level block number (use this as the block identifier). This field is absent on blocks before 1085381001; see the caution note on this page.
Block metadata for the HyperCore block
Block timestamp (ISO 8601)
ABCI round value (not the block number)
Parent ABCI round value
Validator address who proposed this block, as a 0x-prefixed hex string
Hardfork metadata containing version and round
Hardfork version
Hardfork round value
List of signed action bundles in this block; each bundle is a 2-item tuple of [bundle_hash, bundle]
Bundle hash as a 0x-prefixed hex string
Bundle contents
List of signed actions in this bundle
ECDSA signature with r, s, v components
Signature r component as a 0x-prefixed hex string
Signature s component as a 0x-prefixed hex string
Signature v component
The actual operation being performed. The type field identifies the action; see the blocks dataset for the full list of action types.
Action type identifier (e.g., order, cancel, cancelByCloid, batchModify, scheduleCancel, updateLeverage)
Transaction nonce for replay protection
Vault address as a 0x-prefixed hex string. Present only when the action is performed by a vault; the key is omitted otherwise.
Expiry timestamp for the transaction. The key is omitted when no expiry is set.
Indicates the transaction originated from the Hyperliquid frontend. The key is omitted when not set.
Address that broadcasted the transaction bundle
Broadcaster's nonce for the bundle
Responses showing the success or failure of each action in the block
List of responses; each entry is a 2-item tuple of [tx_hash, results]
Transaction hash as a 0x-prefixed hex string
Results produced by the transaction
Address the result applies to, as a 0x-prefixed hex string
Result of the action
Action status: ok when the action executed successfully, err when it failed
Response payload for the action. An object when status is ok, and a plain string carrying the error message when status is err.