Verdict on 0x1b3c…a7c2 eth-mainnet

CredScore sees one or more review-sensitive signals; this case should be manually reviewed before being treated as routine.

Transfers observed: 1201

Wallet age: 5.8 years (2127 days)

Last activity: 0 days ago

Unique counterparties: 578

Sanctions exposure count: 0

Mixer-like interactions: 0

Bridge-like interactions: 7

1. History capped by fetch limitmediumWhy this driver?
   • Transfers observed: At least 1,201
   • History cap: observed count may be a lower bound (cap 1,200)

   Incomplete transfer coverage reduces confidence because observed totals may be lower bounds.

2. High transfer activitymediumWhy this driver?
   • Transfers observed: At least 1,201
   • History cap: observed count may be a lower bound (cap 1,200)

   Higher activity increases interpretive complexity, but should not be treated as adverse on its own unless paired with suspicious concentration, rapid routing, or sensitive exposure.

3. Recognizable entity or protocol contextlowWhy this driver?
   • Observed label: Null / Burn Address
   • Observed label: USDT contract

   Observed counterparties and transfer metadata contain recognizable exchange or protocol context, improving analyst interpretability without by itself determining trustworthiness.

• Established history. Wallet age: 5.8y (observed)Why?
• Recognizable exchange or protocol context. Observed label: Null / Burn Address; Observed label: USDT contractWhy?
• Recognizable protocol attribution. Observed protocol: Null / Burn Address; Observed protocol: USDT contractWhy?

• Improved transaction coverage could materially change activity-based interpretation and increase confidence.
• Stronger counterparty attribution coverage could materially improve interpretability and sharpen the current score.
• Off-chain context would be particularly valuable here, the detected structural patterns raise interpretive ambiguity that on-chain data alone cannot resolve.