Verdict on 0x264b…97b5 ethereum

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

Transfers observed: 501

Wallet age: 3.1 years (1116 days)

Last activity: 0 days ago

Unique counterparties: 252

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 inbound value concentrationmediumWhy this driver?
   • Single source supplied 84% of inbound ETH value
   • Distinct inbound counterparties (all assets): 25

   A large share of inbound value is concentrated in a few transfers, which can indicate a single large unexplained windfall.

3. Review-sensitive fan-out distribution patternmediumWhy this driver?
   • Transfers observed: At least 501
   • Unique counterparties: 252
   • Top counterparty share: 22%

   A review-sensitive fan-out distribution pattern was detected. The structural heuristics indicate this wallet distributes funds to multiple distinct recipients in a compressed fashion that raises review priority when combined with other signals.

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

• 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.