Live flow monitor · tool
Hyperliquid Large Deposit & Orderbook Wall Monitor
Monitor large native USDC deposits into Hyperliquid and unusually large BTC, ETH, and HYPE public L2 orderbook levels, with wall lifecycle changes and clear attribution limits.
Official Hyperliquid app Open Hyperliquid Already used Hyperliquid? If your current address is not eligible, use this link with a fresh wallet address before its first trade. Largest recent deposit — — Open transaction ↗ Largest visible bid wall — — Largest visible ask wall — —
Capital flow console
Large deposits & orderbook walls
Track native USDC deposits into Hyperliquid and unusually large public L2 price levels in one compact view.
Loading monitor
Latest large deposit——
Active walls——
Visible bid walls—Main · HIP-3
Visible ask walls—5-minute collection cycle
00
Large activity
01
Large deposit timeline
Confirmed native USDC transfers to the Hyperliquid Bridge2 contract. The line connects consecutive transfers; it is not cumulative flow.
Deposit amount · USDC
Loading monitor
02
All-market wall radar
Rank every scanned main and HIP-3 market by its largest visible orderbook wall. Click a point to inspect that market.
Visible notional · USD
Loading monitor
Bid-side dominant Ask-side dominant Violet ring = HIP-3
Selected-market wall landscape
Each bubble is a large public L2 price level. Horizontal position is its distance from mark price; height is visible notional.
Visible notional · USD · %
Loading monitor
03
—Wall change tape
Material changes to monitored price levels; select a market above to filter the tape.
Loading monitor
The monitor follows confirmed native USDC transfers into the official Hyperliquid Bridge2 contract and large aggregated BTC, ETH, and HYPE price levels in the public L2 order book. Deposit rows include the sender and transaction hash. An orderbook wall is a price level that can contain multiple orders; it does not reveal the wallets behind them and can be changed or cancelled before execution.
Collection cycle5 minutesThe page refreshes more often, but the underlying monitor runs on one shared five-minute schedule.
Deposit boundaryNative USDCDirect transfers to the official Bridge2 address, not every internal balance change.
Wall boundaryPublic L2 levelsAggregated price levels cannot be attributed to individual wallets.
Continue an investigation from an abnormal event
- Verify the event first. Click a deposit point to open its sender and Arbiscan transaction. Click a market in the all-market radar to inspect the wall distribution around its mark price.
- Check the same market’s context. Use the funding-rate monitor for current holding cost and large-trader positions for the monitored cohort’s main exposure.
- Move to address-level evidence when needed. Inspect a public address in the wallet analyzer or filter the top-position-holder sample by the same market.
- Save the filtered URL. Market, market type, deposit threshold, and wall threshold remain in the URL for repeatable follow-up.
Three common misreadings
- A deposit is not a buy. It confirms a transfer into Bridge2, not the asset or direction traded afterwards.
- A wall is not a fill. Appeared, increased, decreased, and removed describe displayed liquidity—not execution—and one level is not necessarily one whale.
- The filtered view is not the whole market. Thresholds, scanned markets, and collection intervals all affect the number of visible events.
Data scope, collection, and limitations
Large deposits come from native Arbitrum USDC Transfer logs whose destination is the official Hyperliquid Bridge2 contract. A persisted block cursor prevents duplicates. Account-equity changes, PnL, internal transfers, and assets routed through another bridge are not inferred as deposits.
Orderbook walls come from the public L2 book. The monitor calculates displayed notional as price multiplied by aggregate size and stores levels above its collection threshold. One level can contain several orders, and the public book does not reveal the wallets behind them.
The shared Cloudflare schedule collects market events every five minutes. RPC or API failures, confirmation delay, and orders that appear and disappear between snapshots can create gaps. Missing intervals are never replaced with demonstration data.
Frequently asked questions
How can I identify the wallet behind a large Hyperliquid deposit?
Click a point in the deposit chart to reveal the sender address and Arbiscan transaction. This verifies the transfer into Bridge2, but it does not reveal what the wallet traded afterwards.
Does a Hyperliquid orderbook wall reveal who placed it?
No. The public L2 book exposes aggregated size and order count by price, not the placing wallet. One level can contain orders from several participants.
Does this monitor keep historical deposits and wall changes?
It stores confirmed deposit events and material wall events after a level crosses the monitor threshold. Orders that appear and disappear between collection runs may not be recorded.
Are HIP-3 markets included in the wall monitor?
Yes, when they enter the scan queue and exceed the selected notional threshold. The market radar can filter main perpetuals and HIP-3, and uses a violet ring for HIP-3 markets.