Hyperliquid trade flow measures executed activity
Direct answer: it totals official HYPE, BTC, ETH, or SOL trade events received after your tab connects, split by reported side over rolling one-, five-, and fifteen-minute windows. It shows execution activity, not opens versus closes, wallet skill, off-venue hedges, or future direction. Official event schema.
Live executed flow
Rolling totals use only trades received after this tab connects. The first official batch supplies recent context, but never counts toward a completed window. The sample resets when the market or connection changes.
- Reported buy-side
- $0 · 0
- Reported sell-side
- $0 · 0
- Reported buy-side
- $0 · 0
- Reported sell-side
- $0 · 0
- Reported buy-side
- $0 · 0
- Reported sell-side
- $0 · 0
Largest recent prints
Largest reported trades from the initial official batch and this tab's current session.
Recent tape
Initial official context followed by new reported trades received after connection.
Share a complete observed minute
The card becomes available after one uninterrupted minute. It includes the source time, reported-side limitation, and no referral link.
Sharing pauses while the official stream is not live.
Read the sample limitsRead
Executed flow is useful for spotting bursts, participation, and unusually large prints. It becomes misleading when a partial sample is treated as complete positioning or trader intent.
- Rolling totals begin after this browser tab connects; the initial official batch supplies recent context only and is not a historical backfill.
- The browser clears the sample after a reconnect so the page cannot hide an unseen gap.
- Reported buy-side and sell-side events do not reveal whether a trader opened, closed, reduced, or hedged exposure.
- Largest recent prints combine the initial context batch and current session; they are not a complete window, verified whales, or smart-money signals.
- Only HYPE, BTC, ETH, and SOL are available in this first bounded version, one live subscription at a time.
- Wallet addresses and transaction hashes from the public event are not retained, displayed, or sent in analytics.
Read the sample limits
Executed flow is useful for spotting bursts, participation, and unusually large prints. It becomes misleading when a partial sample is treated as complete positioning or trader intent.
- Rolling totals begin after this browser tab connects; the initial official batch supplies recent context only and is not a historical backfill.
- The browser clears the sample after a reconnect so the page cannot hide an unseen gap.
- Reported buy-side and sell-side events do not reveal whether a trader opened, closed, reduced, or hedged exposure.
- Largest recent prints combine the initial context batch and current session; they are not a complete window, verified whales, or smart-money signals.
- Only HYPE, BTC, ETH, and SOL are available in this first bounded version, one live subscription at a time.
- Wallet addresses and transaction hashes from the public event are not retained, displayed, or sent in analytics.
Compare flow with price and positioning
HYPE market brief
Compare the tape with price, base-unit open interest, funding, visible depth, and scheduled TWAPs.
HYPE funding
Separate current carry and completed funding history from short-window executed flow.
Open interest
Check outstanding exposure; trade flow alone does not show whether positions were opened or closed.
Scheduled TWAPs
Compare completed trade events with active indexed schedules without treating either as market-wide intent.
HYPE position size
Turn a risk budget and stop distance into a rounded-down size ceiling before acting on market context.
Data definitions
Review how HypeBasis labels volume, open interest, funding, freshness, and incomplete samples.
Trading after the data check?
The live tape above is context, not a recommendation. If you have already decided to trade, review the eligible referral discount and its limits before opening Hyperliquid.
How to read this dataReviewed 2026-08-25 · ExpandCollapse
- Where this comes from
- Official Hyperliquid mainnet WebSocket trades subscription
- How fresh it is
- Events stream directly to this active tab. The initial batch supplies tape context only; rolling coverage starts at connection and resets after any detected gap, reconnect, market change, or manual reset.
- Last reviewed
- 2026-08-25
- How to use it
- Reported trade side and size are execution context, not verified trader identity, position intent, smart-money status, or a trading signal.
Sources
4 references · ExpandCollapse
- Hyperliquid Docs: WebSocketAccessed 2026-08-25Supports: The official mainnet WebSocket endpoint, subscription messages, and reconnect guidance for live public-data clients.
- Hyperliquid Docs: WebSocket subscriptionsAccessed 2026-08-25Supports: The trades subscription and its coin, side, price, size, timestamp, and trade-ID fields.
- Hyperliquid Docs: Rate limits and user limitsAccessed 2026-08-20Supports: Rate-limit and user-limit constraints for public-data tooling.
- Hyperliquid Docs: Contract specificationsAccessed 2026-08-20Supports: Perpetual contract units, USDC margining, margin fractions, funding versus expiration, and order value limits.