Verdict on 0x56d0…961f ethereum

CredScore sees a 6.1-year-old wallet with at least 364 transfers. History capped by fetch limit and Source return flow detected warrant manual review before this case is treated as routine. Observed entity context: USDT Token, tether.

Transfers observed: 364

Wallet age: 6.1 years (2217 days)

Last activity: 468 days ago

Unique counterparties: 34

Sanctions exposure count: 0

Mixer-like interactions: 0

Bridge-like interactions: 0

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

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

2. Source return flow detectedmediumWhy this driver?
   • Source return count: 2
   • Linked recirculating counterparties: 1
   • Paired mirroring count: 1
   • Repeated amount-band recirculation: 9

   Observed sources later reappear as return destinations, which reduces legibility and suggests recirculating flow rather than clean one-direction settlement.

3. Repeated amount-band recirculationmediumWhy this driver?
   • Source return count: 2
   • Linked recirculating counterparties: 1
   • Paired mirroring count: 1
   • Repeated amount-band recirculation: 9

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

• Established history. Wallet age: 6.1y (observed)Why?
• Moderately distributed counterparties. Unique counterparties observed: 34Why?
• Material attribution coverage. Attributed interaction share: 100% (68% high-confidence)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.
• 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.