Verdict on 0x22b8…38c2 eth-mainnet

CredScore sees a 9.9-year-old wallet with at least 501 transfers. History capped by fetch limit and High transfer activity warrant manual review before this case is treated as routine. Observed entity context: transfer, Binance USD (BUSD).

Transfers observed: 501

Wallet age: 9.9 years (3620 days)

Last activity: 390 days ago

Unique counterparties: 378

Sanctions exposure count: 0

Mixer-like interactions: 0

Bridge-like interactions: 0

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

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

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

   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. Stale recent activitymediumWhy this driver?
   • Days since last observed activity: 390

   A long gap since last activity reduces the freshness of the observable signal.

• Established history. Wallet age: 9.9y (observed)Why?
• Recognizable exchange or protocol context. Observed label: transfer; Observed label: Binance USD (BUSD); Observed label: Null / Burn AddressWhy?
• Recognizable protocol attribution. Observed protocol: Null / Burn Address; Observed protocol: Binance USD (BUSD)Why?

• Improved transaction coverage could materially change activity-based interpretation and increase confidence.
• Fresh activity could change this classification because the current signal is not recent.
• Off-chain context would be particularly valuable here, the detected structural patterns raise interpretive ambiguity that on-chain data alone cannot resolve.