Press figures for the frozen total differed by half a billion dollars, so this article rebuilds the evening from the token contracts: every freeze Tether and Circle wrote, every transfer into and out of the frozen addresses, and their balances at each freeze and on 12 November 2026. The result: about $2.58 billion is frozen today, $2.17 billion of it on addresses we traced by their transfers to the sweep. Where we rely on someone else, we say who.

A sweeper on Binance 14 at 20:20 UTC

According to a public reconstruction by on-chain researchers (Monitoring The Situation: Binance wallet incident), at 20:20:59 UTC an attacker used an EIP-7702 authorization signed for the Binance 14 hot wallet to attach "sweeper" code to it, then emptied it. The same reconstruction says nothing in the record explains how the signing access was obtained. What the token contracts show for certain: at 20:24:23 UTC, 1,615,409,498.97 USDT left Binance 14 for 0x5227…2f8c, followed 24 seconds later by 55,739,800.50 USDT from Binance 16. Binance 14 and Binance 16 are public explorer labels for Binance hot wallets.

Timeline of 29 October 2026 from 20:24 to 22:06 UTC: money moving out of Binance wallets on the left, Tether and Circle freezes on the right
Source: Etherscan and TronGrid event logs, read 12 November 2026; Binance labels from public label data, the cold wallet from Arkham proof-of-reserves data.

The 37 minutes before the first freeze

The receiving address held 1,671,149,299.47 USDT at 20:24:47. It did not keep all of it. At 20:30:11 it sent 500,000,000 USDT to 0x9749…C762, and at 20:33:23 another 200,000,000 USDT to 0x0ddf…697e. Between 20:41 and 20:59 it also received 823,000,000 USDC from Binance Hot Wallet 34 (a Binance hot wallet in public label data).

21:01:35 UTC: Tether froze the main receiving address, with 971,149,299.48 USDT on it (the extra 0.01 came from a look-alike address at 20:31, the kind used for address poisoning), 37 minutes after the first sweep. In the same Ethereum block it froze 0x9749…C762, and twelve seconds later 0x0ddf…697e. Both were already empty: 0x9749 had passed its 500 million on in ten transfers between 20:34 and 20:59, and 0x0ddf had put about 10 million into trading pools at 20:47 and sent the other 190 million onward at 20:52. Circle froze the same main address at 21:04:59, locking the 823 million USDC.

TrustSniffer's freeze tracker logged Tether's freeze proposal for the main address at 20:59:11 UTC (a Tether freeze starts as a transaction submitted to Tether's multisignature wallet, which its keyholders then approve), 144 seconds before the freeze executed, and the address's wallet page reads Blocked, 100 out of 100.

Twenty minutes of chasing

Tether then froze addresses further down the trail, some in time and some not:

  • 21:02:47 0x8d53…639a, the address that had received 190M from 0x0ddf: already empty.
  • 21:09:12 TG5i…zsGi on TRON: 312,729,468 USDT frozen.
  • 21:14:59 0xAa24…54a0: 174,999,872.33 USDT frozen, almost all of the 175M it had received at 21:08 from an address that took 175M from 0x9749 at 20:59.
  • 21:18:59 0xb171…c8c3: 30,000,000 USDT frozen, received 168 seconds earlier from 0xCcBE…a263, which Tether had frozen empty at 21:16:47. We did not trace how 0xCcBE was funded, so we count this one as frozen in the same window.
  • 21:21:12 TCzB…7Y62 on TRON: 65,990,000 USDT frozen.
  • Also frozen empty: 0x7Aa4…bfd1 at 21:12:35 and TPBk…KN4 on TRON at 21:17:39.

Of the twelve addresses Tether froze between 21:01 and 22:06, six were already empty. The researchers' reconstruction puts the money that left Binance across seven blockchains that evening at about $5.85 billion, and calls that a gross figure, not Binance's final loss. For the TRON addresses we checked only their freeze events and balances, not the transfers that reached them, so we list them as frozen in the same twenty minutes rather than as traced.

The 200 million that arrived after the freeze

We have not seen this part of the record reported. USDT kept being swept into an address Tether had already frozen. At 21:04:23, three minutes after the freeze, another 3,917,639.77 USDT went from Binance 14 into 0x5227…2f8c. Then, at 21:42:59, 200,000,000 USDT arrived in Binance 14 from 0x2213…bc9e, an address Arkham's proof-of-reserves data lists as a Binance cold wallet. Seventy-two seconds later, at 21:44:11, 200,397,771.82 USDT was swept from Binance 14 into the frozen 0x5227 (transaction 0x55ba4dab…0556). We checked each transaction: all three sweeps, at 20:24, 21:04 and 21:44, were sent by the same caller address, 0x7c86…5ca0, calling Binance 14. Whoever sent them did not stop for the freeze, and the contract accepted them.

We do not know whether that cold-wallet transfer was an automatic hot-wallet refill or a manual one, and the record does not say. What it does show is why the freeze mattered: Tether's contract stops a blacklisted address from sending USDT, not from receiving it. Everything that lands there after the freeze stays there. The main address held 971,149,299.48 USDT when it was frozen and 1,175,464,712.88 USDT on 12 November: the two later sweeps plus 1.81 USDT of dust that unrelated addresses sent it afterwards. None of it has moved. The 204 million that arrived after the freeze was swept out of Binance 14, and 200 million of it had just come from a wallet Arkham labels as Binance cold storage, so on that evidence it was Binance's money. It is now stuck there rather than in the hands of whoever swept it.

22:06:23: Tether froze Binance 14 itself, with 1,351,530.01 USDT on it at that block. Two weeks later it is still on Tether's blacklist and holds 1,352,017.99 USDT. Circle froze it too, at 23:53:35, with 52,363.12 USDC on it. Binance 14 looks like a deposit-consolidation wallet: its history is a steady stream of small incoming transfers, the pattern of customer deposits being swept in, and its balance has grown by only 488 USDT since the freeze. What the freeze means for Binance's internal accounts is for Binance to say; on-chain we can only see that the address remains frozen.

Bar chart of the balances on the six funded frozen addresses, the main one shown once for USDT and once for USDC, at the moment of each freeze and on 12 November 2026, totalling about 2.58 billion dollars
The red segment is USDT that arrived after the freeze. Source: Etherscan and TronGrid, balanceOf at each freeze block and on 12 November 2026; TrustSniffer analysis.

How much is frozen: $2.38B, $2.58B or $1.79B

  • At the moment of each freeze: about $2.38 billion. Tether froze 1,556,220,169.82 USDT across six funded addresses, and Circle 823,052,363.12 USDC on two (the main address and Binance 14). That is close to the $2.3 billion some outlets reported.
  • Today: about $2.58 billion (1,760,536,071.20 USDT and 823,052,363.12 USDC), because 204.3 million USDT reached the main address after it was frozen.
  • The $1.7 to $1.8 billion headlines match the sum of Tether's first and biggest freeze (971 million) and Circle's 823 million, $1.79 billion, without the later freezes.

None of these balances has been destroyed. Tether's contract can burn the USDT on a blacklisted address, and it did so on other addresses after 29 October (13 times on Ethereum and 21 times on TRON), but not on any address in this article.

What this means if you hold or accept USDT

  • A frozen address still accepts USDT, and keeps it. If you send USDT to an address on Tether's blacklist, the transfer goes through and the money cannot move unless the issuer acts. USDC works differently: Circle's contract refuses transfers into a blacklisted address, which is why no USDC reached the main address after Circle's freeze. Before you pay a wallet you have not paid before, check it in the USDT freeze tracker, and for why a balance called USDT can be fake, see how to check that TRC20 USDT is genuine Tether.
  • An exchange wallet can be frozen too. Binance 14 has been on the blacklist since 29 October. Your balance on an exchange is a claim on the exchange, not a balance on one address, so a frozen hot wallet does not by itself freeze your account. Binance says user funds are safe and that it covers the losses from its SAFU fund and its own funds.
  • Money that passed through these addresses can be flagged. About 700 million USDT left the main address before the freeze and went through further wallets and trading pools. Exchanges screen deposits against addresses like these. If a large USDT payment reaches you from a wallet you do not know, run it through our on-chain risk check first; the receiving addresses we found are listed for security teams below.
  • For anyone running hot wallets: check the refills. We do not know whether the 200 million USDT moved into Binance 14 from cold storage, 79 minutes after it was first drained, was an automatic top-up. If it was, the lesson is general: a hot wallet that still carries someone else's code (here an EIP-7702 delegation, according to the researchers) passes on whatever arrives, so halting automatic top-ups and revoking the delegation come first.
  • Expect "unfreeze" scams. Every large freeze in the news is followed by offers to recover frozen USDT for a fee. Only the issuer can lift a freeze, and it does not sell that service. See how the USDT unfreeze scam works.

How to check whether an address is frozen

  1. USDT on Ethereum: open Tether's contract 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Etherscan, choose Contract, then Read Contract, and enter the address in getBlackListStatus. "true" means frozen.
  2. USDC on Ethereum: open 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48, choose Read as Proxy, and use isBlacklisted.
  3. USDT on TRON: open TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on Tronscan, choose Contract, then Read, and use getBlackListStatus.
  4. Or look it up in one step in TrustSniffer's USDT freeze tracker, which lists every issuer freeze on Ethereum and TRON as it happens, or with the wallet check.

For exchanges and security teams

The addresses frozen on 29 October 2026, with the balance at the freeze (all still frozen on 12 November 2026), the key transactions, the caller behind the sweeps, and the unfrozen addresses that received USDT from 0x9749 before its freeze. Screen inbound deposits against the whole list and alert on the unfrozen recipients; trading pools are left out because ordinary traders use them.

# Ethereum, USDT (Tether), UTC
0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c  21:01:35  971,149,299.48  (now 1,175,464,712.88)
0x9749292D74Fd460982d0912eA9515EA24736C762  21:01:35  0
0x0Ddf0480016E6bcb2c1f5D190D221FBa1320697e  21:01:47  0
0x8d53903625b8e839B9DF4bd28b0Efb1cD6b8639a  21:02:47  0
0x7Aa4D3029e4c6A8E916300014Ad95b6d6C03bfd1  21:12:35  0
0xAa246BF639586a6Ba46762D378CE50cA4fc654a0  21:14:59  174,999,872.33
0xCcBEF95633aDb5cD2b5038Db5a38D77e726Ca263  21:16:47  0
0xb171cA86f82070282138352Ff7111b494060c8c3  21:18:59  30,000,000.00
0x28C6c06298d514Db089934071355E5743bf21d60  22:06:23  1,351,530.01  (Binance 14)
# Ethereum, USDC (Circle)
0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c  21:04:59  823,000,000.00
0x28C6c06298d514Db089934071355E5743bf21d60  23:53:35  52,363.12  (Binance 14)
# TRON, USDT (Tether)
TG5iBMQPrDzJJAUM8GMVBf1hRaJ1wvzsGi          21:09:12  312,729,468.00
TPBkSjkCMn2ckrMuAP8n2J1jdjbw76bKN4          21:17:39  0
TCzBTkqn66yApqbYoPezaEQosM5DAd7Y62          21:21:12  65,990,000.00
# Key transactions (Ethereum)
0x53bd38b816c23e74134786c29a8c18d792777998a3b9326047b583100e88e2f3  20:24:23  1,615,409,498.97 USDT Binance 14 -> 0x5227
0x68d7d69deaeb9750c38020b4f8d3728146ca8d2267eba1e38cf9b56722ad659a  20:30:11  500,000,000 USDT 0x5227 -> 0x9749
0x1fc0ef33a767132edad434834a5555b30fcb5a171206c03b86175ef6dafac81c  20:33:23  200,000,000 USDT 0x5227 -> 0x0ddf
0x7baba482077843514d9c72bac0110ba0916b0814288a72917e2c3bb27a9d8659  21:01:35  Tether freeze of 0x5227 (block 26300954)
0x31c4c9fe287d54fb9d3b79980477a8c793a11f774b98d0a9a92de1dad888a91d  21:04:23  3,917,639.77 USDT Binance 14 -> 0x5227 (frozen)
0xc954c86f118e8e410e6a3eb9e3b38ff4a95fbdae9d2d58e13166afb7a1f4fc5f  21:04:59  Circle freeze of 0x5227
0xf56867f0b81faa1ac92fd99492398ff089886aa11fb41288529178813062a1c6  21:42:59  200,000,000 USDT cold wallet -> Binance 14
0x55ba4dabc41b468e580751373ad31acdee6f5ba398682df2c93e5a8340870556  21:44:11  200,397,771.82 USDT Binance 14 -> 0x5227 (frozen)
# Caller of all three sweeps (sent the transactions to Binance 14)
0x7c8601d4645b93cea45f71e118a729332e6b5ca0
# Not frozen: received USDT from 0x9749 before its freeze (20:34 to 20:59).
# These received funds; they are not confirmed attacker wallets and may be MEV, solver or router infrastructure. Check before blocking.
0x74edc79fea13bdf1f7841570227127cec493bdd9  50,000,000      contract (could be a router or pool: check first)
0x0000000000be226afde21672a5e4adc45692e69d  100,000,000     EIP-7702 delegated account
0xbeef02961503351625926ea9a11ae13b29f5c555  145,000,000     EIP-7702 delegated account (four transfers)
0x9b1303ebf09bc51b7fac376c9e421e8daae63b82  28,600,454.37   contract (could be a router or pool: check first)
0xec4fb7e7c35c241e1138a2d8cfbb09f3ad1ccb22  1,399,545.64    small contract (two transfers)
0x811f15855476156ebf86ba3b84fafb8ceaa4e84c  175,000,000     wallet (passed on to 0xAa24, frozen)

Live freezes on both networks are on the USDT freeze tracker, and the totals behind it are in the Risk Index. Every freeze of that day is in our daily freeze report for 29 October 2026, and how often a wallet flagged from Tether's own proposals ends up frozen is in 99.5% of flagged USDT wallets were frozen.

What we could not establish

  • How the signing access to Binance wallets was obtained, and by whom. The researchers' reconstruction says the same.
  • Where the roughly 700 million USDT that left before the freeze ended up. We followed it two hops, into further wallets and trading pools, and stopped.
  • Whether the two funded TRON addresses received money from the same incident. They were frozen in the same twenty minutes; we did not trace their incoming transfers.
  • Whether the 200 million USDT from the cold wallet was an automatic refill, and how Binance accounts for the funds frozen on its own wallet.

How we checked

  • Freezes: Tether's AddedBlackList events and Circle's Blacklisted events on Ethereum (from Etherscan logs) and Tether's AddedBlackList events on TRON (from TronGrid), with the block time of each.
  • Money movements: every USDT and USDC transfer into and out of the frozen addresses on 29 October, from Etherscan, read on 12 November 2026.
  • Balances: balanceOf on the token contracts at each freeze block and again on 12 November 2026; getBlackListStatus and isBlacklisted to confirm every address is still frozen.
  • TrustSniffer's own record: the freeze tracker entry and wallet page for each frozen address (linked where it appears above).
  • Labels: Binance 14, Binance 16 and Hot Wallet 34 are labels from public label data; the cold wallet is labelled in Arkham's proof-of-reserves data. The EIP-7702 detail comes from the researchers' public reconstruction, which TrustSniffer did not verify independently.

Frequently asked questions

I received USDT from 0x9749 or 0x0ddf before they were frozen. Is my money frozen?

No. A freeze applies only to the address that is blacklisted, and only from that moment on. USDT that left those addresses before 21:01 UTC is not frozen by it. Exchanges may still screen a deposit that came from them, so keep the transaction hashes and the time you received it.

How long does a Tether freeze last?

Until Tether removes the address from its blacklist; there is no fixed term. Some freezes are lifted and many never are. Every removal is a public event on the token contract, and our freeze tracker records those too.

How much was taken in the Binance hack?

Binance dates the hot-wallet attack to about 20:05 UTC on 29 October 2026 (the first Ethereum event in this article is at 20:20) and said it cost about $6.3 billion in tokens, and that about $3 billion had been frozen with industry partners. The researchers' reconstruction counts about $5.85 billion in gross transfers across seven blockchains. This article covers only the USDT and USDC frozen on Ethereum and TRON.

Did Circle freeze any USDT?

No. Circle issues USDC and can only freeze USDC; it froze 823 million USDC on the main receiving address. Every USDT freeze in this article was Tether's.