Skip to content
TraceFast Docs

Blacklisted

Open Blacklisted in TraceFast →

Blacklisted / Compliance view

What it shows

Some token contracts can freeze funds. Centrally-issued stablecoins and wrapped assets — USDT, USDC, and hundreds of others — ship an admin function that adds an address to an on-chain blacklist, after which it can no longer send or receive that token. Every one of those actions is a public transaction. The Blacklisted view watches for them across every freeze-capable contract TraceFast tracks and turns the raw events into a live compliance feed.

:::tip Sign-in required (free account) Blacklisted is for signed-in users: signed out, the page shows Sign in to open this section. A free account is enough; see Account & Security. :::

The header counters summarize the current state:

  • Total Blacklisted — the size of the currently-frozen address set across all tracked contracts.
  • Added / Removed (24h) — freezes and un-freezes in the last day, with the net change.
  • Tracked Contracts — how many freeze-capable contracts are under watch (550+).

Top Blacklist Contracts ranks issuers by how many addresses each currently holds blacklisted — a quick read on which tokens do the most freezing. It names the issuer doing the freezing, not the frozen address. Each row is a link: it opens Currently Blacklisted filtered to that issuer's frozen addresses.

Every contract on this page — in the chart and in both tables — carries an authority badge that says how much a freeze from it means:

  • issuer — a recognized issuer (e.g. a regulated stablecoin); its blacklist is authoritative.
  • arbitrary — a token's self-run blacklist; low authority, and it does not imply the subject is broadly sanctioned.

The distinction matters more than the raw counts: XSGD freezes more addresses than USD Coin, but one is an arbitrary self-blacklist and the other a regulated issuer acting on legal process.

:::info The lists are verified issuers only The chart and both tabs cover only contracts whose identity is verified, and the page says so beneath the chart — 14 verified issuers of 562 blacklisting contracts. The events and addresses below cover only these issuers — freezes by contracts whose identity is not verified are not shown on this page. Plenty of unverified contracts run their own blacklists, some of them freezing many addresses; the header counters still count them, the lists do not. Read the chart as "who among the identifiable issuers freezes most", not as the overall leaderboard, and an address missing from the lists as "not frozen by a verified issuer". :::

How to read it

Two tabs split the same data by question:

  • Currently Blacklisted — the standing set: who is frozen right now, rather than the moment they were frozen.
  • Events — the chronological feed. Each row is one on-chain action: the target address that was frozen, the contract that froze (or un-froze) it with its authority badge, when, the transaction that carried it (the link opens the transaction on its Events tab — the blacklist log itself), the event name as the contract emitted it (Blacklisted, AddedBlackList, BlackListed — issuers name it differently), and the action (add / remove). When the target is a known entity, its label is shown inline — a frozen address tagged as a sanctioned or malicious entity is the row worth reading first.

A freeze is issuer-level, not protocol-level: it is the token's operator exercising control the token was designed to allow, and it only affects that one token. The same address can be frozen by one stablecoin and untouched everywhere else. Reading a target's entity page shows the fuller picture — every label and counterparty, not just this one freeze.

Check an address

Blacklist verdict for a checked address

The question the page exists to answer — is this address on a blacklist? — has a direct control. Paste an address into the Check an address 0x… field between the chart and the tabs, or click Check this address next to any row. The page reloads with ?address= in the URL (so a verdict is shareable as a link), both tabs filter to that address, and a verdict banner appears above them:

  • Blacklisted by recognized issuer (red) — an authoritative freeze; the banner names the issuing contract(s).
  • Not blacklisted by any recognized issuer. Flagged by N arbitrary token contracts (amber) — only self-run blacklists have frozen it. Low authority, not a sanction.
  • Not blacklisted by any of the N tracked contracts (green) — clean across the full corpus.

Clear drops the filter and returns to the unfiltered view. The verdict is a statement about the tracked blacklist corpus, not a general sanctions screen — an address can be absent from every token blacklist and still be worth reading in full on its entity page.

Data & update cadence

Events are decoded from on-chain logs as blocks are ingested, so the feed tracks the chain in near real time; the counters and the currently-blacklisted set update with it. History runs back across the tracked contracts, so an address's freeze events stay visible after the fact.

Last updated 22 Oct 2026, 08:06 UTC · verified against TraceFast v1.0.261 · Markdown