Verdict on 0x2767…f482 ethereum

CredScore sees a 16-day-old wallet with at least 44 transfers. History capped by fetch limit and High inbound value concentration warrant manual review before this case is treated as routine. Observed entity context: transfer, 1inch.

Transfers observed: 44

Wallet age: 0.0 years (16 days)

Last activity: 5 days ago

Unique counterparties: 38

Sanctions exposure count: 0

Mixer-like interactions: 0

Bridge-like interactions: 0

1. History capped by fetch limitmediumWhy this driver?
   • Transfers observed: At least 44
   • 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 >99% of inbound ETH value
   • Distinct inbound counterparties (all assets): 36

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

3. Repeated amount-band recirculationmediumWhy this driver?
   • Repeated amount-band recirculation: 2
   • Funding dependency concentration: 10%
   • Multi-hop pressure: 22/100

   Repeated reuse of the same transfer size bands across a narrow routing set can indicate mechanical flow or recirculation rather than broad organic usage.

• Moderately distributed counterparties. Unique counterparties observed: 38Why?
• Recognizable exchange or protocol context. Observed label: transfer; Observed label: 1inch; Observed label: 1inch RouterWhy?
• Recognizable protocol attribution. Observed protocol: 1inch; Observed protocol: USDT contractWhy?

• Improved transaction coverage could materially change activity-based interpretation and increase confidence.
• As more history accumulates, this address may stabilize into a clearer behavioral profile.
• Improved data coverage for missing core metrics would likely improve confidence and may affect the trust score.