TV1ErMvnSFdGdhH6GNYZMj5trV5Z6QHBMJ

Tron USDT Wallet Frozen by Tether: On-Chain Blacklist Event

Case Overview

This wallet on the Tron network was added to Tether's blacklist on August 27, 2026, effectively freezing its USDT holdings. The on-chain record shows an AddedBlackList event for the USDT contract, with a balance of 92,966.46 USDT at the time. The wallet's activity reveals a significant incoming flow from another address that is also blacklisted, pointing to a likely reason for the freeze.

Freeze Event Timeline

• 2026-08-27 13:16:18 UTC: Tether executed an AddedBlackList transaction on the Tron network for this wallet. The transaction hash is f0952a9698a3409cd1ae7ea58739cc95403544f6757722b0065cf6a07a240669.
• The observed balance at that moment was 92,966.460892 USDT, which is now frozen.
• The wallet had been active before the freeze, with transfers tracked from September 2025 to August 2026.

Possible Reasons for the Freeze

The most concrete signal is the wallet's direct receipt of 164,707.52 USDT from TFB5wGzo8T3oWW675Z1ZpQ7XMGggFGHoPC, an address that is itself blacklisted by Tether. This one-hop exposure is a common trigger for issuer action. Additionally, a rapid pass-through flow was observed: 3,800 USDT arrived and 3,500 left within 23 minutes, which can indicate automated or suspicious activity. While the exact rationale is not public, the combination of these patterns likely contributed to the blacklist decision.

Funds, Labels, and Counterparties

No labels or sanctions matches were found for this wallet, and no entity attribution is possible from the available data. The primary counterparty is the blacklisted address mentioned above, which accounts for over 32% of tracked volume. Other inflows come from a range of addresses, but none carry known labels. The wallet also sent funds to many addresses, including a notable outflow of 74,193 USDT to TD9TKmsLHBYAQgTHKBFhZazXfL53wPNcHP across 85 transactions.

Reader Caveats

• This analysis is based on on-chain data and does not include Tether's internal reasoning for the blacklist.
• The transaction history is limited to the provider's tracking window and may not capture all activity.
• The presence of a blacklist event does not automatically imply criminal activity; it may be precautionary or related to regulatory requirements.
• This page is for informational purposes only and should not be treated as legal or compliance advice.