Crypto futures liquidations reach $87 million, PANews reports: check your contract and window

What the $87 million report actually contains

PANews attributes the figures to CoinGlass and describes a rolling 24-hour period. Its precise total is $86.9994 million, rounded to $87 million in this headline. The report assigns $52.9224 million to long liquidations and $34.0769 million to short liquidations. Those are reported liquidation values, rather than a count of traders or a measurement of deposits leaving exchanges. The original report lists the total and directional components.

The same report gives BTC liquidations of $13.7953 million and ETH liquidations of $12.7351 million. Adding those produces $26.5304 million. Dividing that sum by the reported $86.9994 million total gives approximately 30.49%. That calculation describes the combined BTC and ETH share of this particular reported liquidation value. It does not describe their share of open positions or trading volume.

PANews also identifies the largest individual liquidation as HYPERLIQUID-XPL-USD, worth $1.6838 million. That contract label matters. A reader holding BTC should not treat the largest order in this report as a BTC liquidation, and a reader holding XPL should not treat it as the total liquidations for XPL. The source supplies an individual order figure and a contract label; it does not supply a complete XPL market breakdown. The contract and order amount are in the PANews report.

There is a small arithmetic detail worth preserving when checking the numbers. The reported long and short amounts add to $86.9993 million, which is $100 below the stated total. We retain the source's figures and use its stated total for the percentages. The discrepancy does not support a claim about missing liquidations or a specific platform; resolving it would require the underlying unrounded records.

Our Binance and OKX observation has another scope

The NexuAlpha feed generated at 00:43:08 SGT on November 2 records a 24-hour total of $38,298,258 across its Binance and OKX observations. Its long component is $17,744,820 and its short component is $20,553,438. The components add exactly to the displayed total. The feed records 20,134 orders in that window. These fields are in the 24-hour liquidation object.

Using that total, $20,553,438 divided by $38,298,258 gives a short share of approximately 53.67%. Longs account for the remaining approximately 46.33%. The calculation is useful for describing the balance of the observations in this feed. It does not turn the feed into a duplicate of CoinGlass's dataset.

The largest order in this NexuAlpha window is labelled OKX:ETHUSDT, short, with a value of $880,423. Its recorded time is 01:46:09 SGT on November 1. It therefore belongs to a different contract and observation set from the HYPERLIQUID-XPL-USD order in PANews. Selecting the bigger of these two values would not identify a newly verified largest order across both providers' full coverage.

The NexuAlpha liquidations board lets readers inspect our observations alongside their stated coverage. When comparing it with an external headline, retain the feed generation time and the Binance plus OKX label. A screenshot without those fields cannot preserve the conditions under which the number was observed.

Why the directional balances differ

PANews's reported set is long-heavy by liquidation value. Our later Binance and OKX observation is short-heavy. Both descriptions follow from arithmetic on their respective inputs. The difference alone cannot tell us which venue, instrument or intervening minute accounts for the gap, because the source sets do not match.

A valid claim that liquidations switched from longs to shorts would need comparable observations over successive periods. Here, both the observation time and the coverage change. Assigning the difference entirely to time would ignore the venue change; assigning it entirely to venue would ignore the different endpoint. The available figures cannot separate those effects.

The same issue prevents a calculation of Binance and OKX's share of the reported $87 million. Dividing our total by PANews's total would produce a number, but the numerator and denominator belong to different snapshots. Calling the result a venue market share would imply a matched set of observations that we have not established.

Subtracting the totals would be equally unhelpful. It would not measure liquidations outside Binance and OKX, because the two sources have different observation conditions. Nor could it show that liquidation activity disappeared between the publications. Keep each total beside its own timestamp and coverage instead of combining them into an unsupported market statistic.

A rolling window needs its endpoint

The PANews report appeared at 23:30 SGT on November 1. Our snapshot was generated after midnight, at 00:43:08 SGT on November 2. The date change can make the figures look like consecutive daily reports. Both are described as 24-hour observations, and neither should be relabelled as a completed Singapore calendar day.

For a rolling 24-hour comparison, a different endpoint also means a different starting point. The later window can include newer observations while excluding older ones. We cannot calculate those additions and exclusions from a pair of aggregate totals with different coverage. Doing so would require records that connect the two windows on the same basis.

When saving a comparison, write down the period label as well as the time: 24 hours, the source's publication or generation timestamp, and the venues stated by that source. If you later compare another snapshot, keep those fields consistent. This makes it possible to tell whether a change belongs to the measurements or to the way the measurements were selected.

How to use the figures when checking a position

1. If you hold a position on Binance or OKX, check your own position or closed-order record. Copy the exact contract symbol, long or short direction, and event time. Match that venue and time with the observation you are reading before comparing amounts. A reported long liquidation figure describes that source's long-side observations; it cannot explain the handling of a short position without further contract-level information. The aggregate is a context check, while your account record identifies the position involved.

2. For that same Binance or OKX contract, inspect the margin amount and liquidation price displayed in your position record. Save both with their timestamp, then consult the terms attached to that contract if a figure needs explanation. Keep the account figures separate from the public liquidation total; the aggregate does not calculate your position threshold.

If an order has already closed, compare its recorded direction and execution time with the window you are reading. An event outside that window should not be explained by the window's directional split. For an open position, use the current position information in your account when reviewing exposure; neither the $87 million headline nor our observed short share supplies a future price or your own liquidation threshold.

Readers comparing public figures can return to the liquidations board and record a fresh timestamp. Keep that new observation separate from the snapshot used here. A refreshed page may be useful for a current check, but replacing the original time silently would make the article's arithmetic impossible to reproduce.

What the opened sources do not settle

We read PANews's account of CoinGlass data and our own venue observation feed. We did not independently reproduce the CoinGlass total from its underlying order records. Our feed provides a separate observation of Binance and OKX; it does not independently verify PANews's exact $86.9994 million figure.

The sources also do not establish a cause for the reported liquidations. The figures alone cannot attribute them to a particular news event, wallet movement or change in exchange operations. Any explanation naming a trigger would need additional evidence linking that trigger to the relevant contracts and times.

Quick answers

Does $87 million mean that amount left exchanges?

The PANews figure is reported futures liquidation value. The opened report does not measure withdrawals, net exchange outflows or the number of people who lost funds. Use the reported category when repeating the number.

Can long-heavy and short-heavy readings both be accurate?

They can describe different observation sets. Here, PANews's reported figures imply approximately 60.83% longs, while our Binance and OKX snapshot implies approximately 53.67% shorts. Their coverage and endpoints differ, so the balance of one cannot validate or invalidate the other by itself.

Is the $1.6838 million XPL order the same as our largest ETH order?

The source labels identify different contracts. PANews names HYPERLIQUID-XPL-USD; our snapshot names OKX:ETHUSDT and gives $880,423 for a short liquidation. Keep each order attached to its own source and window when comparing them.