Docs
Docs
Home
Getting Started
Agent Tooling
CLI
Supported Chains
Acala
Aptos
Arbitrum
Arc
Asset Hub
Astar
Avalanche
Base
Berachain
Bifrost
Binance Smart Chain
Bittensor
Blast
Boba Network
Bridge Hub
Celo
Centrifuge
Chiliz
Cronos
Enjin
Ethereum
Etherlink
Flow EVM Gateway
Gnosis
Hydration
Hyperliquid
Immutable
Ink
IoTeX
Kusama
Linea
LISK
Manta Atlantic
Manta Pacific
Mantle
MegaETH
Monad
Movement
Neuroweb
opBNB
Optimism
Plasma
Polkadot
Polygon
Pulsechain
Robinhood
Ronin
Scroll
Sonic
Starknet
Taiko
Tempo
Sui
TRON
Unichain
Viction
World Chain
XDC Network
XX Network
Zetachain
zkSync Era
Zora
Supported ChainsHyperliquidData CatalogDerived data

Hyperliquid Trades - Live Trade Prints

Understand Hyperliquid V3 trade batches, participant fields, live access, and historical alternatives.

Hyperliquid RPC endpoint: endpoint URLs, plans and pricing.

Trades are normalized match records for tape displays, execution analytics, and market-flow signals. Each trade reports the taker side, execution price and size, transaction hash, match identifier, and every bid-side and ask-side participant.

Access

AvailabilityAccessDetails
LiveStreamTradesProvides typed V3 gRPC trade batches.
LiveOrder Book WebSocket tradesProvides live JSON trade messages and an optional user filter.
HistoricalHyperliquid Index fillsProvides a historical alternative.
HistoricalTick dataProvides a historical alternative.
ArchivalS3 BucketProvides archival fill records for custom processing.

Live behavior

StreamTrades accepts 1-20 coins and an optional user filter. It batches matches by (block, coin).

bid_users and ask_users are repeated fields because a match can contain multiple makers. A self-trade can place the same address on both sides.

Within one block, identify a match by (coin, tid). Across blocks, include the batch's block_number in the match key.

The gRPC stream is live-only. It has no opening snapshot and no historical replay. ABORTED means frames were lost or live state reset. Reconnect for new activity, then use an archival or indexed alternative to recover any missed interval.

Sample data

This synthetic V3 protobuf payload uses visible redaction markers instead of production identifiers:

protobuf
time: 1785736814057
block_number: 1058646974
trades: {
  coin: "<redacted-market>"
  side: "B"
  px: "114250.0"
  sz: "0.75"
  hash: "<redacted-transaction-hash>"
  time: 1785736814057
  tid: 99887766
  bid_users: "<redacted-bid-user>"
  ask_users: "<redacted-ask-user>"
  ask_users: "<redacted-second-ask-user>"
  synthetic: false
}

The Order Book WebSocket represents the same participant set in a single users array. The V3 gRPC payload keeps bid-side and ask-side users separate.

Related pages

  • Whale tracking guide — Build real-time alerts around large, attributed trades.
  • Order book WebSocket guide — Combine trades with L2, L4, and multi-coin routing.
  • Derived fill views — Move from match-level trades to participant-specific execution records.

Hyperliquid Periodic ABCI State - Binary Data

Understand periodic_abci_states RMP files, their layout, and archival, dedicated gRPC, or snapshot access paths.

Hyperliquid L2 Books - Snapshots and Diffs

Maintain Hyperliquid aggregated order books with V3 snapshots, sequenced diffs, and WebSocket alternatives.

On this page

AccessLive behaviorSample dataRelated pages