Data sources
TRON USDT screening data sources and freshness
TRON Checker reads public TRON data and cached sanctions datasets to produce independent freeze and OFAC facts plus explainable risk indicators. This page documents source roles, freshness, and limitations without listing screened or sanctioned addresses.
Risk scores are informational indicators only. They are not legal advice, a compliance determination, or an automated accept/reject instruction.
Source classes
| Source | Role | Freshness | Confidence / coverage | Limitations |
|---|---|---|---|---|
| TronScan stablecoin blacklist index | Independent indexed view of USDT blacklist status on TRON. | Checked during screening with bounded timeouts and retries; blacklist responses can be cached for up to 60 seconds. | When the live contract read is unavailable, freeze confidence may fall back to TronScan-only evidence at 90. | Index lag is possible; disagreement with the contract is reported as inconclusive. |
| Tether USDT TRC20 contract (via TronGrid/TronWeb) | Direct on-chain blacklist status for the screened address. | Live contract read during each check. | Successful contract reads set freeze confidence to 100. | Network or RPC failures make the freeze fact incomplete rather than inventing a result. |
| Local Tether event history | Supplemental AddedBlackList, RemovedBlackList, and DestroyedBlackFunds evidence. | Synced on a recurring schedule and attached as supplemental history. | Supports review; does not override primary dual-source freeze status. | History can lag; removed or destroyed-funds events remain evidence-only. |
| OFAC TRON dataset cache | Exact normalized match against cached OFAC TRON identifiers. | Refreshed on a schedule; generation timestamp is published with aggregate metadata. | Fresh data: 100; aging: 92; exact match on stale data: 85; unavailable: 0. Stale negative screens are unavailable. | Only exact matches; no fuzzy or multi-chain address rewriting in this product. |
| OpenSanctions collections | Legal-sanctions matches and separate crime-intelligence matches for TRON wallets. | Updated on a schedule and recorded in source-health runs. | Legal-sanctions matches act as hard signals; crime matches contribute bounded derived points. | Collections can be empty or unavailable without inventing matches. |
| Chainabuse moderator-verified reports | Public intelligence for verified TRON reports. | Checked at analysis time with a privacy-preserving short-lived cache. | One or more verified reports contribute a single bounded risk-indicator addition. | Report narratives and submitted addresses are not retained for marketing or SEO pages. |
| TronScan TRC20 transfers, tags, and balances | Public transfer windows, entity tags, balances, exposure, and flow heuristics. | Fetched during signed-in analysis within timeouts and page caps. | Pagination and sampling reduce confidence caps on affected evidence; locked checks appear in coverage. | Transfer history is bounded and may be truncated; 2-hop tracing is sampled, not exhaustive. |
OFAC cache metadata
Aggregate metadata only. Individual sanctions identifiers are not published on this page.
- Cached TRON identifiers
- 260
- Dataset generated at
- 2026-07-08T04:12:56.992Z
Privacy boundaries
- Only public TRON addresses are screened. Seed phrases and private keys are never requested.
- Marketing and SEO pages do not list screened wallets or sanctions identifiers.
- Saved reports and watchlists are opt-in authenticated features, not public indexable pages.
- Analytics sanitization avoids sending raw addresses to third-party analytics.