FEATURED

How a Frozen TRON Wallet Lost Another 512,000 USDT in 10 Days

On July 10, 2026, Tether froze a TRON wallet holding 5.57 million USDT. Nobody on the receiving end noticed. For the next ten days the money kept coming: 12 more deposits, 512,912 USDT in total, every one of them frozen the moment it landed. Below is the whole story with a link to every transaction, and the ten-second check that would have saved all of it.

A busy wallet, until the evening of July 10

The address TQY2E1mz…g1sy4b was created on May 29, 2026 and looked like thousands of active TRON wallets. In six weeks it took in 7.57 million USDT: deposits of a few thousand USDT almost every weekday, larger ones from 40,000 to 1.2 million, mostly from the same few counterparties. It also paid out: 100,000 USDT on June 1, 1.7 million on June 5 and 200,000 on June 23. That last transfer, 4e6407c9…, is the final time this wallet moved a single USDT.

On July 10, 2026 at 18:32 UTC, Tether added the address to its blacklist. The transaction is public, c038c341…, and so is the result: 5,566,672.65 USDT frozen in that block. Less than three hours earlier, at 15:38 UTC, the wallet had accepted a routine deposit of 3,743.14 USDT (d6ef7b25…). Nothing on the screen changed after the freeze. The balance still showed 5.57 million. It just was not money anymore.

Ten days of deposits into a dead address

This is the part that should make anyone who moves USDT uncomfortable. The freeze did not stop a single incoming transfer. Between July 11 and July 20, twelve more deposits arrived from four addresses, two of which had been paying this wallet for weeks:

Date (UTC)Amount, USDTSenderTransaction
July 11, 15:1657,584.00TV8Wni…N1HBb64ca218…
July 13, 16:2011,462.07TGDFDy…Lkw5a7fc56b6…
July 13, 21:1183,268.00TV8Wni…N1HB7bef33d2…
July 14, 12:35122,273.12TBn9xQ…kD7G55136c06…
July 14, 13:042,233.25TGDFDy…Lkw5c76d488d…
July 15, 13:523,353.22TLhBiE…Q3mbdb05f18d…
July 16, 14:023,026.44TLhBiE…Q3mb030a0afc…
July 17, 14:374,017.35TLhBiE…Q3mb8bf4103b…
July 17, 17:0645,733.52TBn9xQ…kD7G49416b4c…
July 17, 19:0379,054.00TV8Wni…N1HBec62d23f…
July 20, 14:4810,467.36TLhBiE…Q3mb08c929da…
July 20, 21:5090,440.00TV8Wni…N1HBc1d6d2ab…

Total: 512,912.33 USDT. Whether the owner was topping up their own wallet or counterparties were paying for something, the outcome is the same: each transfer was frozen in the very block that confirmed it, and nobody can pull it back.

The moment somebody finally noticed

It took a week. On July 17 at 10:01 UTC the wallet tried to send 70,000 USDT and the network rejected the transaction with the status REVERT (1b50d77a…). Twenty minutes later, the same amount and the same result (beb0fa2c…). Then the attempts grew bigger: 2,000,000 USDT on July 19 (571d49c8…), 50,000 that evening (4946a8bd…), 180,000 and 2,500,000 on July 20 (17b1f8d8…, 34902325…), one last 2,500,000 on July 23 (e664b14c…). Every one of them failed. Every one of them burned fees for nothing.

Now the detail that turns bad luck into negligence. On July 20 at 21:50 UTC, six hours after two failed withdrawals that same afternoon, another 90,440 USDT arrived (c1d6d2ab…). In total, five deposits worth 229,712 USDT came in after the first failed withdrawal on July 17. Somebody already knew the address was frozen, and the money kept flowing in anyway.

On November 6, 2026, we queried the USDT contract directly. isBlackListed still returns true, and 6,079,584.98 USDT still sit on the address. Four months later, not a single token has moved.

Why a frozen wallet keeps accepting money

USDT is not like TRX or Bitcoin. It is a token issued by one company, Tether, and the smart contract behind it has a blacklist. When an address is added, usually after a request from law enforcement or a flag from Tether's own compliance team, three things happen at once: the address can no longer send USDT, it can still receive USDT, and nobody gets a notification. Your wallet app shows a successful transfer. The recipient sees the balance go up. The only thing that changed is that the money now belongs to the freeze, not to anyone you know. Only Tether can lift it, through a legal process, not through a support chat.

The freeze itself is not a secret. It is an event written into the contract, and anyone can check the status of any address in seconds. The owner of this wallet did not. Neither did the people who sent it 512,912 USDT.

What this means for you

Three rules, and this wallet broke all of them:

  1. Check the destination before every large transfer, even if you paid the same address yesterday. On July 10 this wallet was clean at 15:38 and frozen at 18:32. A status that was fine last week says nothing about today.
  2. If you receive USDT regularly, check your own receiving address from time to time. A freeze can be triggered by funds that passed through your counterparties. Whoever paid you can be the reason your address ends up on the list.
  3. A failed transfer is an alarm, not a glitch. The first REVERT on July 17 was the moment to stop every incoming payment. Instead, another 229,712 USDT arrived.

Ten seconds that were worth 512,912 USDT

A wallet check with AML Verifier shows exactly what was missing here: whether the address is on the Tether or Circle freeze list and since when, whether it appears on OFAC sanctions lists (the US Treasury office that keeps the list of sanctioned people and addresses), and what its risk score looks like based on where its funds came from. It takes seconds, you pay per check with no subscription, and it works on the website and in the Telegram Mini App.

Check a wallet or transaction with AML Verifier before you send or accept USDT, and if you move USDT on TRON often, read our guide on how to check a USDT TRC20 wallet. One check on July 11 would have cost a few dollars. Not running it cost 512,912 USDT. Don't be this wallet.