Verdict on 0x264b…97b5 ethereum

CredScore sees a 3.2-year-old wallet with at least 501 transfers. History capped by fetch limit and Balance unavailable warrant manual review before this case is treated as routine. Observed entity context: transfer, USDC Token.

Transfers observed: 501

Wallet age: 3.2 years (1162 days)

Last activity: 0 days ago

Unique counterparties: 291

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. Balance unavailablemediumWhy this driver?
   • Native balance: Unknown

   Missing core metrics reduce confidence and increase the chance of misclassification.

3. Bursty activity patternmediumWhy this driver?
   • Average observed activity: 501.9 tx/day

   A compressed activity window can indicate non-routine behavior and deserves added caution.

• Established history. Wallet age: 3.2y (observed)Why?
• Recognizable exchange or protocol context. Observed label: transfer; Observed label: USDC Token; Observed label: circleWhy?
• Recognizable protocol attribution. Observed protocol: LINK token contract; Observed protocol: circle; Observed protocol: Uniswap UNI TokenWhy?

• Improved transaction coverage could materially change activity-based interpretation and increase confidence.
• Improved data coverage for missing core metrics would likely improve confidence and may affect the trust score.
• Off-chain context would be particularly valuable here, the detected structural patterns raise interpretive ambiguity that on-chain data alone cannot resolve.