Overview

The blocks stream (stored as replica_cmds) contains ALL raw L1 transactions submitted to the Hyperliquid blockchain. This is the most comprehensive dataset available, capturing every action on the chain.

Stream Type: BLOCKS
API Availability: gRPC Streaming API only
Volume: Extremely High - Every L1 action is recorded
Availability: gRPC nodes only

Data Structure

Each block contains:

• Block metadata (abci_block)
• Signed action bundles (transactions with signatures)
• Responses (resps) showing success/failure of each action

{
  "abci_block": {
    "round": 1096693511,
    "parent_round": 1096693510,
    "time": "2025-12-04T08:00:47.509497915",
    "proposer": "0x9dd85fb6cf95a9d755af0853b36fb05e972c71e1",
    "hardfork": {
      "version": 69,
      "round": 1091072071
    },
    "signed_action_bundles": [
      [
        "0xhash...",
        {
          "signed_actions": [
            {
              "signature": {
                "r": "0x...",
                "s": "0x...",
                "v": 28
              },
              "action": {
                "type": "order",
                "a": 0,
                "b": true,
                "p": "92385.0",
                "s": "0.00361",
                "r": false,
                "t": {"limit": {"tif": "Gtc"}},
                "c": "0x89119db7aae18b90abe620888af9aadc"
              },
              "nonce": 1764816505537,
              "vaultAddress": null
            }
          ],
          "broadcaster": "0x...",
          "broadcaster_nonce": 1764816362065
        }
      ]
    ]
  },
  "resps": {
    "Full": [
      [
        "0xhash...",
        [
          {
            "user": "0x...",
            "res": {
              "status": "ok",
              "response": {
                "type": "default"
              }
            }
          }
        ]
      ]
    ]
  }
}

Block Metadata Fields

Field

Type

Description

round

integer

Block number (use this as the block identifier)

parent_round

integer

Previous block number

time

string

Block timestamp (ISO 8601)

proposer

string

Validator address who proposed this block

hardfork

object

Current protocol version and activation block

Transaction Fields

Field

Type

Description

signature

object

ECDSA signature with r, s, v components

action

object

The actual operation being performed (see Action Types)

nonce

integer

Transaction nonce for replay protection

vaultAddress

string|null

Present when action is performed by a vault

broadcaster

string

Address that broadcasted the transaction bundle

broadcaster_nonce

integer

Broadcaster's nonce for the bundle

Complete Action Types (34 Types)

All L1 transaction types are organized by category for easier understanding:

Category

Action Types

Purpose

Trading

order, cancel, cancelByCloid, modify, batchModify, scheduleCancel

Place, modify, and cancel orders

TWAP Orders

twapOrder, twapCancel

Time-weighted algorithmic trading

Asset Transfers

usdSend, spotSend, sendAsset, withdraw3, usdClassTransfer

Move funds between accounts and off-platform

Account Management

createSubAccount, subAccountTransfer, updateLeverage, updateIsolatedMargin

Sub-accounts, leverage, and margin settings

Vault Operations

vaultTransfer, NetChildVaultPositionsAction, approveAgent

Vault deposits, withdrawals, and agent permissions

Builder & MEV

approveBuilderFee

MEV builder fee approvals and payments

Referrals

registerReferrer, setReferrer

Referral program registration and attribution

Market Deployment

perpDeploy

Launch new perpetual markets

Token Operations

tokenDelegate

Token delegation for governance/staking

EVM Operations

evmRawTx, evmUserModify

Direct smart contract interactions

DEX Abstraction

agentEnableDexAbstraction, userDexAbstraction

Unified DEX interface and advanced trading

Validator & Governance

ValidatorSignWithdrawalAction, VoteEthFinalizedWithdrawalAction, SetGlobalAction

Bridge security, governance, protocol upgrades

Multi-Signature

multiSig

Transactions requiring multiple approvals

Utility

noop

Protocol synchronization and placeholder transactions

Key Action Details

Action

Description

Key Fields

order

Place new orders on the exchange

a, b, p, s, r, t, c

cancel

Cancel orders by order ID

a, o

twapOrder

Place algorithmic TWAP orders

duration, randomization

usdSend

Send USD between users

destination, amount, fee

withdraw3

Withdraw funds from platform

destination, amount

vaultTransfer

Transfer to/from vaults

vault, amount, direction

evmRawTx

Raw EVM transactions

RLP encoded data

perpDeploy

Deploy new perpetual markets

market parameters

Field Abbreviations:

• a = asset, b = is buy, p = price, s = size, r = reduce only, t = order type, c = cloid, o = order ID

Response Structure

The resps field contains the result of each action:

{
  "Full": [
    [
      "0xtransaction_hash",
      [
        {
          "user": "0xuser_address",
          "res": {
            "status": "ok",  // or "err"
            "response": {
              "type": "default"  // or specific response data
            }
          }
        }
      ]
    ]
  ]
}

Status values:

• "ok" - Action executed successfully
• "err" - Action failed (response contains error message)

API Usage

gRPC Streaming Only

// Subscribe to blocks (gRPC only)
const request = {
  subscribe: {
    stream_type: 'BLOCKS',
    start_block: 0,
    filters: {
      "action_type": ["order", "cancel", "twapOrder"],
      "user": ["0x123..."]
    }
  }
};

Note: This dataset is only available on gRPC nodes, not through JSON-RPC or WebSocket APIs.

Important Notes

1. gRPC Nodes Only: This dataset is only available on gRPC nodes, not on regular full nodes
2. Block Identifier: Use round as the block number, not the file name
3. Responses Required: Always check resps to see if actions succeeded or failed
4. Highest Volume: This is the highest volume dataset - each block can contain thousands of actions
5. Most Comprehensive: This captures EVERYTHING on L1 - if it happened on Hyperliquid, it's here
6. Raw L1 Data: This is the raw blockchain data before any processing or aggregation
7. Signature Verification: All actions include ECDSA signatures for verification
8. Vault Actions: Actions from vaults include vaultAddress field

Related Streams

• Orders - Processed order events derived from raw order actions
• Trades - Trade executions resulting from order matching
• Events - Processed blockchain events derived from various actions
• TWAP - TWAP order status updates from twapOrder and twapCancel actions