Verdict on 0xdb27…a8fe eth-mainnet

CredScore sees a 5.4-year-old wallet with at least 501 transfers. High-confidence sanctions attribution and History capped by fetch limit are severe enough to require escalation before any further interaction.

Transfers observed: 501

Wallet age: 5.4 years (1961 days)

Last activity: 353 days ago

Unique counterparties: 97

Sanctions exposure count: 0

Mixer-like interactions: 0

Bridge-like interactions: 0

1. High-confidence sanctions attributionhighWhy this driver?
   • This wallet itself is on a sanctions watchlist (per the curated registry or OFAC SDN sync).

   Sanctions-sensitive attribution materially increases review urgency because legal and compliance context becomes critical.

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

3. Source return flow detectedmediumWhy this driver?
   • Source return count: 8
   • Repeated amount-band recirculation: 17
   • Funding dependency concentration: 12%
   • Multi-hop pressure: 6/100

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

• Established history. Wallet age: 5.4y (observed)Why?
• Moderately distributed counterparties. Unique counterparties observed: 97Why?
• Material attribution coverage. Attributed interaction share: 100% (13% high-confidence)Why?

• 0xdb2720ebad55399117ddb4c4a4afd9a4ccada8fe ↗0xdb2720ebad55399117ddb4c4a4afd9a4ccada8fe · DERAKHSHAN · OFAC_SDN
  Synced from OFAC SDN CSV

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