Auto-deleveraging (ADL)

Auto-deleveraging (ADL) means the venue reduces or closes profitable positions on one side of a market to cover liquidations on the other side that the market could not absorb.

Definition

Auto-deleveraging (ADL) means the venue reduces or closes profitable positions on one side of a market to cover liquidations on the other side that the market could not absorb. The trader placed no order; the venue cut the position.

In one sentence: Auto-deleveraging (ADL): the venue cuts profitable positions on one side to cover liquidations on the other side that the market could not absorb.

Current data · all markets

no data yet
Auto-deleveraging (ADL)
timecoinside cutUSD cutwalletsopposite liquidations
4 Nov 2026, 04:19 UTCBTClong$16.8M26$5.9M

From the data shown above: First row: 4 Nov 2026, 04:19 UTC, coin BTC, side cut long, USD cut $16.8M, wallets 26, opposite liquidations $5.9M.

How we compute it

Formula

possible ADL = ≥ 3 tracked wallets cut profitable positions on one side by ≥ $5M within 10 minutes
while ≥ $5M of the opposite side was liquidated on Hyperliquid (cooldown 60 minutes per coin)
  • The detector does not see ADL fills directly, so ADL is inferred: it compares position polls of the tracked wallets with the stored liquidations every minute.
  • An event fires when, within 10 minutes, at least 3 tracked wallets reduced or closed positions that were in profit at the poll before, together $5M or more on one side of a coin, while $5M or more of the opposite side was liquidated.
  • Severity 2, from $25M cut severity 3. Each event is published on Security › Latest with the wallets and amounts as evidence.
  • On Lighter, trades flagged as auto-deleveraging are not counted as liquidations.

How to read it

  • An event names the coin, the side that was cut, the USD cut and the opposite liquidations in the same window.
  • Several events in a short time on one coin point to a market that could not absorb its liquidations.

Common mistakes

  • Taking every event as confirmed ADL. It is a pattern match on public positions; the venue does not confirm it.
  • Counting ADL as liquidations. The cut positions were in profit; they are not part of the liquidation totals.

Honest limits

  • Voluntary profit-taking into a liquidation cascade looks the same; the event says “possible” for that reason.
  • Only tracked wallets are seen; ADL of positions the collector does not poll is missed.

Questions and answers

Can Blockmetric confirm that a position was auto-deleveraged?

No. The detector does not see ADL fills directly; it infers ADL from tracked positions that were in profit and shrank while the opposite side was liquidated. Voluntary profit-taking looks the same, so every event says possible.

Use it live

Step by step

API

Every key uses the data of its plan; see the developer docs for parameters and examples. Developers · API docs

Plan availability

  • Free: every coin, current values and 30 days of history.
  • Pro and above: history up to 1095 days, CSV export.
  • API: free developer key (10/min, 1,000/day, free-tier data, non-commercial) · API Dev and above (60/min, 50,000/day).

Pricing → · Historical data

Terms defined here

Auto-deleveraging (ADL)

Methodology. Facts from public data. Not investment advice. · Report incorrect data

LiveHyperliquid markets 13sOperationalHyperliquid positions & whales 10sOperationalLiquidation heatmap & levels 17sOperationalLighter markets & liquidations 17sOperationalLighter positions & heatmap 13sOperationalLighter RH positions & heatmap 12sOperationalBinance markets 46sOperationalBybit markets 1mOperationalBinance liquidations 23sOperationalBybit liquidations 23sOperationaldYdX positions & heatmap 22sOperationalGMX positions & heatmap 11sOperationalLong/short & open interest history 21sOperationalOrder books & trade flow 10sOperationalOn-chain transfers 9sOperationalSecurity monitor 41sOperationalBlockmetric Sentiment 3mOperationalOfficial news 6mOperationalAlert delivery 9sOperational10:14:41 UTCData: Blockmetric Research · Binance · Bybit