Binance deposits exceed withdrawals on an hourly basis right now, the exchange said on Tuesday, as Binance user activity starts to pick up after the Binance $6 billion hack. The shift came by 03:00 UTC on November 3, after days of heavy Binance hack withdrawals and billions in Binance crypto outflows.
In the update confirming that Binance deposits exceed withdrawals, the exchange said:
“By 03:00 UTC, we are seeing hourly deposits exceed withdrawals, reflecting improving user activity and stabilizing flows.”
Withdrawal data update
— Binance (@binance) November 3, 2026
By 03:00 UTC, we are seeing hourly deposits exceed withdrawals, reflecting improving user activity and stabilizing flows. pic.twitter.com/UiXmYC2lm3
Binance Hack Recovery, $6 Billion Outflows and User Confidence

The update matters because Binance deposits exceed withdrawals after two days in which money mostly flowed one way. Binance turned withdrawals back on in phases on Sunday, November 1, three days after the Binance $6 billion hack. It also plans to reopen more assets and networks, and Binance user activity has picked up since then, based on its own data.
How Big Were The Binance Crypto Outflows?
During the first nine and a half hours, Binance processed $4.649 billion in withdrawals against $1.01 billion in deposits, a net outflow of about $3.64 billion, or 2.1% of its $171 billion in assets. Co-founder Changpeng “CZ” Zhao said on X that the bulk of the net outflow landed in the first couple of hours, when the Binance hack withdrawals hit their peak.
The bigger picture is heavier, even if Binance deposits exceed withdrawals today. Binance’s own hourly chart, which runs from 06:00 UTC on November 1 to 04:00 UTC on November 3, put total Binance crypto outflows at $10.97 billion, against $5.695 billion in deposits, for a net outflow of $5.276 billion. The worst hour came at 08:00 UTC on November 1, when withdrawals hit $1.243 billion and the net outflow reached $936 million. USDT, USDC and BTC made up the biggest share of what users pulled out.
After that, the hourly gap kept shrinking. Binance logged net deposits in six separate hours on November 2 and early November 3, and in the 03:00 UTC hour it took in $193 million in deposits against $183 million in withdrawals. That is why the news that Binance deposits exceed withdrawals on an hourly basis carries so much weight right now.
How Binance Is Covering The $6 Billion Hack
Binance says it is paying for the losses with its own money and its Secure Asset Fund for Users (SAFU). Co-CEO Richard Teng made that promise soon after the Binance $6 billion hack, when he said:
“We are committed to covering all hacked losses through our company funds.”
By Sunday, the exchange had covered about 95% of the stolen assets, up from around 90% a day earlier, and it keeps buying the remaining less liquid tokens through open-market and OTC deals. Major coins, including BTC, ETH, USDT, BNB, SOL, USDC and XRP, are fully backed at 100%. It also plans to refill SAFU to about $1 billion. When withdrawals restarted, Teng stated:
“Binance will absorb the financial impact of the stolen funds, not our users.”
Users now get to test that pledge, and the fact that Binance deposits exceed withdrawals suggests many of them are sticking around.
Also Read: Musk’s Fortune Falls $48.5B as SpaceX Stock Drops 40% From Peak
What It Means For Binance Users
Right now, the fact that Binance deposits exceed withdrawals is the best sign yet that the rush to pull funds has slowed. At the time of writing, Binance user activity is picking back up, and the Binance hack withdrawals look more like a short burst than a lasting exodus. A $3.64 billion net outflow in under ten hours is a lot of money, but it equals just 2.1% of the $171 billion Binance reported before the attack, and the Binance crypto outflows have cooled off.
Binance deposits exceed withdrawals for now, but the exchange still has to buy back the last missing tokens and publish its updated proof-of-reserves report.





Comments (0)
Please sign in to comment.
No comments yet. Be the first to comment.