TGbZV6bYA8f66v6e7CnvSGbZBj7W45PRiD

Issuer blacklist event

On 1 September 2026 at 20:06 UTC, Tether posted an AddedBlackList event for USDT on Tron for wallet TGbZV6bYA8f66v6e7CnvSGbZBj7W45PRiD. The on-chain balance visible at the time was 3,763.085482 USDT. The event appears in TronGrid data under transaction 706e416b... and is the clearest signal that the issuer has frozen USDT held at this address.

This is an issuer-controlled freeze, not a chain-level or protocol-level stop. Tether operates the USDT blacklist on the TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t contract, and the wallet now matches that blacklist. In practical terms, the USDT in this address is blocked from normal transfers unless Tether later removes the address from the list.

Most likely freeze drivers

The public evidence does not state why Tether acted. Compliance teams should treat the blacklist as the primary signal, not as proof of a specific crime.

The scan gives the wallet a CRITICAL risk rating (100) and specifically flags a direct issuer blacklist match. Two behavioral patterns stand out but are secondary:

• A rapid pass-through flow: 300,000 USDT arrived and 345,855.92 USDT left within 45 minutes.
• A time-of-day anomaly: 83.9% of tracked transfers took place inside the same three-hour UTC window.

These patterns can appear in legitimate treasury or allocation workflows, so they do not prove why the blacklist was applied. The likely driver remains the issuer's own determination that the address should not receive, hold, or send Tether USDT.

Funds and counterparties

The scan identifies one funding source: TAzsQ9Gx8eqFNFSKbeXrbi45CuVPHzA8wr. No exchange, service provider, or business label is attached to that address.

On the inbound side, the largest counterparties include TNn55e7MFrPNFHUYyJcN3NaEd1kuvMd299 with about 13.7m USDT across 64 transfers and TCvEfZKVWKm56Z4UovWG9v5UjuvSh1nPUf with about 5.94m USDT across 29 transfers. On the outbound side, significant destinations include TDvu7sfjURciHaJfEWqZYgioMau1Kzaf9w (about 10.39m USDT) and TWALXcrY5b4WaNUTzZsBsyKqBj7N6vmSxf (about 6.32m USDT).

These counterparties are unlabeled in the available data. Their low risk category in the scan reflects the absence of a known flag, not a confirmation that they are safe to transact with. The original source of funds is not confirmed.

Signals for compliance teams

• Treat this address as a Tether-blacklisted USDT wallet on Tron. Any incoming USDT from it should be reviewed and likely rejected.
• Do not assume the freeze is limited to the current balance; issuer blacklists typically block the address's ability to transact in that asset.
• Watch for indirect exposure: if your counterparties interact with this wallet, their flows may carry inherited risk.
• Consider the behavioral flags (rapid pass-through, narrow time window) when reviewing addresses connected to the same funding source.

The immediate compliance action is straightforward: avoid accepting USDT from this wallet and document the issuer blacklist finding in your risk case.

Evidence and limits

The main evidence is the on-chain AddedBlackList event, the matching issuer blacklist contract, and the wallet's observed balance. That evidence is strong for Tether froze this wallet. It is not sufficient to identify the owner, the jurisdiction, or the underlying reason.

No verified labels or ownership data were found in the supplied dataset. The transfer totals are based on the tracked TRC20-USDT window, not a complete historical ledger for every asset. Issuer freeze reasons may also change if the address is later removed from the blacklist.

Bottom line: this is an issuer-frozen USDT wallet on Tron. The freeze action is confirmed; the motive and ownership are not.