How much leveraged crypto was force-closed in the last hour, four hours and 24 hours on Binance and OKX futures, split into long and short positions.
Source: Binance USDT-M force-order stream + OKX liquidation orders
The feed refreshes every few minutes. Nothing is estimated while it is missing — try again shortly.
Observed lower bound · Longs liquidated / Shorts liquidated · USD · SGT
The feed refreshes every few minutes. Nothing is estimated while it is missing — try again shortly.
A liquidation happens when a leveraged futures position loses so much margin that the exchange force-closes it. The position is sold (long) or bought back (short) at market, which often pushes the price further in the same direction.
A long squeeze is a wave of long liquidations during a fall; a short squeeze is the mirror image during a rally. When both columns are large in the same window, longs and shorts were both wiped out — traders call this a double kill (多空双杀): a sharp move in one direction followed by a sharp reversal.
The figures come from Binance's public force-order stream, which sends at most one order per symbol per second, plus OKX's liquidation-order endpoint for BTC, ETH, SOL, XRP and DOGE. They are a lower bound for two exchanges, not the whole market, and they are not investment advice.
A liquidation is the forced closing of a leveraged position by the exchange when its margin falls below the maintenance requirement. The trader loses the margin; the exchange closes the position at market to stop further losses.
Long liquidations happen when the price falls, short liquidations when it rises. The split shows which side of the market was caught out. Large numbers on both sides in the same window point to a sharp move followed by a reversal (多空双杀).
From Binance's public USDT-M force-order WebSocket stream and OKX's public liquidation-orders API, aggregated by NexuAlpha every five minutes. Binance sends at most one order per symbol per second, so the totals are a lower bound and cover only these two exchanges.
The collector rewrites the feed every five minutes and the page re-reads it every 60 seconds while open. The timestamp above the numbers shows when the feed was last generated, in SGT.
Articles in the NexuAlpha library on this subject, most-read first, each with its sources listed.
All articles