Binance reports $3.64 billion net outflow over 9½ hours

Gross withdrawals and net outflow answer different questions

The largest flow number in the detailed report is $4.649 billion. That is the amount Binance said it processed in withdrawals during the specified interval. It describes money moving out before deposits are deducted. The $3.64 billion headline is the net figure, after incoming deposits offset part of the outgoing amount.

Using PANews' more precise withdrawal figure, the arithmetic is $4.649 billion − $1.010 billion = $3.639 billion. Rounding to three significant figures produces $3.64 billion. Starting with CNBC's rounded $4.65 billion instead gives $3.64 billion directly. Those presentations are consistent at the headline's precision; there is no need to invent an extra flow to reconcile them.

Deposits equal about 21.7% of gross withdrawals in this window: $1.010 billion ÷ $4.649 billion × 100. This is our calculation from the reported totals. It measures the scale of incoming funds relative to outgoing funds during those hours. It does not identify which customers deposited, why they did so, or whether anyone withdrew and later returned money.

A net total can hide those distinctions. Someone following withdrawal processing wants to know the gross amount handled. Someone comparing the balance of incoming and outgoing funds wants the net figure. The two questions use the same source figures, but replacing one label with the other changes the meaning of the answer.

None of this arithmetic measures the incident's loss. Adding the post-reopening net outflow to a separately reported loss would combine customer transfers with a different category of movement. The sources opened for this article do not supply a reconciliation that would justify such a combined total.

Keep the 9½-hour period attached to the number

The measurement begins at 14:00 SGT on November 1 and ends at 23:30 SGT that day. CNBC states the interval as 06:00–15:30 UTC, which converts to the same SGT times. The elapsed period is nine hours and thirty minutes. It is not a full-day total, and a report appearing on November 2 does not move those flows into a new measurement period.

That boundary matters when another headline quotes a different outflow number. Before treating it as a contradiction or a fresh acceleration, compare its start time, end time and definition. A later ending time can include transfers outside this interval. A gross withdrawal measure can exceed a net measure even when both describe the same hours.

Dividing the calculated $3.639 billion net outflow by 9.5 gives an average of roughly $383 million per hour over the whole window. That is an arithmetic average, not an observed hourly series. It cannot tell readers which hour was busiest, whether a queue cleared at a particular minute, or what happened after 23:30 SGT.

Both PANews and CNBC report Binance's statement that withdrawals eased after an initial surge while deposits remained substantial. Their readable accounts do not provide an hour-by-hour table. We therefore retain the direction as Binance's description and do not draw a chart or extend the average into a forecast for the following day.

For the same reason, multiplying this average by twenty-four would produce an unsupported daily projection. The reported pattern itself describes changing activity. A fixed-rate extrapolation would discard that change while giving the result the appearance of a measured total.

Why the stated 2.10% needs its own label

The reports place the net outflow beside $171 billion in total assets, using proof-of-reserves data dated October 28. They quote the proportion as 2.1%, or 2.10% in PANews. The asset figure is a dated denominator. It is not a freshly measured balance taken at the end of the withdrawal window.

Dividing the displayed inputs gives a slightly different result: $3.639 billion ÷ $171 billion × 100 = about 2.128%, or 2.13% to two decimal places. Using the rounded $3.64 billion numerator gives about 2.129%. Neither calculation reproduces 2.10% exactly from the published figures.

The gap is about 0.028 percentage points when the more precise numerator is used. The opened reports do not explain whether underlying unrounded values or another calculation produced the quoted percentage. We report 2.10% as the attributed figure and 2.13% as our calculation from the displayed inputs. We do not silently replace one with the other.

The percentage also cannot be turned into a count of customers. Dollar value and number of account holders are different denominators. These reports supply no account-level distribution for the withdrawal window. They do not show how many customers left, how many stayed, or what fraction of any one customer's balance moved.

A reserve comparison can help describe the scale of a flow against a dated asset figure. It cannot establish the present status of every withdrawal route or the receipt of a particular transfer. Those questions require information about the route and transaction concerned.

Fifteen first-phase routes do not mean every route

According to PANews, phased reopening began at 14:00 SGT on November 1. By 20:36 SGT, the fifteen networks and assets in the first phase had resumed withdrawals. CNBC gives the corresponding completion time as 12:36 UTC. The elapsed time between the reported start and that milestone is six hours and thirty-six minutes.

The scope qualifier matters: fifteen refers to the first phase described in the reports. Both accounts say testing continued for the remaining networks and assets. Readers should therefore avoid interpreting the milestone as a statement that every asset on every network was available.

Neither opened report supplies the full list of those fifteen entries. This article consequently does not identify a particular token-network combination as currently open. If your transfer uses a route outside the announced first phase, the aggregate milestone supplies no schedule for that route.

In your existing Binance account, open the record for the pending withdrawal and read the asset, selected network and displayed processing status together. If there is a transaction identifier, compare it with the receiving service's record for that same transfer. If there is no identifier yet, keep the request time and reference available when asking official support about the pending request.

For a receiving exchange, also check the deposit instruction currently shown for that asset and network. An outbound service becoming available does not itself verify the receiving side's requirements. Review any destination field that the receiving screen requires before sending another transfer; do not copy it from an unrelated earlier transaction.

A new reserve snapshot is a separate document

PANews reports that Binance said a new proof-of-reserves snapshot was completed at 08:00 SGT on October 31, with an updated report expected on November 2. That is a reported publication expectation. This article has not verified a newly released reserve report, so the October 28 denominator remains explicitly dated whenever it is used here.

A snapshot time, a report's release time and the flow window are different dates in this story. If an updated report appears, compare the period it measures with the November 1 transfer interval before using it as a new denominator. Publication on a later day does not automatically make its underlying snapshot later than every transaction discussed here.

Keep the published asset total and its measurement date together in any note you save. If the denominator changes in a later update, recompute the percentage and say which denominator you used. Preserve the original window's withdrawals and deposits unless a source actually revises those numbers.

What to check while a withdrawal is pending

Use the account and official support route you already know. A message offering to unlock a withdrawal or arrange compensation through a separate wallet transfer should not become part of your transfer procedure. Do not follow unsolicited compensation links or send funds to a supposed recovery address received in a direct message.

Record what you can observe: the request's timestamp, the asset-network pair, the status shown by the sender and any corresponding entry at the recipient. Those observations are more useful for resolving your transfer than a screenshot of the exchange's aggregate net outflow. They also allow you to distinguish an update to your request from a general reopening headline.

The next useful reporting would specify another measurement window, give the remaining routes' status, or publish the promised reserve report with its snapshot date. Until then, $3.64 billion refers to the attributed net outflow over the stated nine and a half hours. The individual transfer still needs its own receipt check.

Quick answers

Is $3.64 billion a full-day outflow?

The reported window covers 14:00–23:30 SGT on November 1, nine and a half hours. A full-day comparison needs its own start and end times.

Does net outflow measure newly stolen funds?

This net figure is withdrawals minus deposits. The reports do not provide a reconciliation that would turn it into an additional incident-loss amount.

What should a customer verify next?

Check the asset-network route and the individual withdrawal record, then compare any transaction identifier with the recipient's record. For a new reserve report, retain its actual snapshot date when comparing asset figures.