Wallet risk report
- Address analysed
- 0x6f65d9d651a08ae0a1f8975dd534bddce9be1139
EVM
Invented wallet and transactions, flagged counterparties from the real lists, frozen prices.
Risk score
5.7% of the value received comes from counterparties in the Mixer category (Tornado Cash).
- Alerts
- 2
- Counterparties
- 10
- Active networks
- 3
Alerts
2-
High risk
Mixer
Funds received · Tornado Cash
- Share
- 5.7% of the value received
- Value
- $900
- Movements
- 3
- Counterparties
- 1
- Last seen
- 15 Oct 2026
OFAC lifted its sanctions on Tornado Cash on 21 Mar 2025: its contracts count as a mixer, not as sanctions.
-
Low risk
Sanctions
Dust received · Lazarus Group
- Share
- under 0.1% of the value received
- Value
- $0.36
- Movements
- 1
- Counterparties
- 1
- Last seen
- 20 Oct 2026
- Sanctions programs
- DPRK3
- OFAC entry created on
- 13 Sep 2019
Less than $25 received and nothing sent back: dusting, a weak signal that is never critical.
Exposure by category
Where the value received comes from and where the value sent goes, by category of direct counterparty, at current prices.
Received
Total $15,680
-
Sanctions under 0.1%$0.36
Movements: 1 · counterparties: 1
-
Mixer 5.7%$900
Movements: 3 · counterparties: 1
-
DeFi 23%$3,580
Movements: 1 · counterparties: 1
-
Exchange 48%$7,500
Movements: 1 · counterparties: 1
-
Unidentified 24%$3,700
Movements: 2 · counterparties: 2
Sent
Total $8,310
-
Bridge 12%$1,000
Movements: 1 · counterparties: 1
-
DeFi 67%$5,600
Movements: 2 · counterparties: 2
-
Unidentified 21%$1,710
Movements: 2 · counterparties: 2
Identification
This address
On none of the lists.
Identified counterparties
77%
77% of the volume involves a counterparty the lists identify.
Main counterparties
Counterparties in total: 10
Direct counterparties, flagged categories first, then by value.
| Counterparty | Category | Networks | Received | Sent |
|---|---|---|---|---|
| Lazarus Group 0x098b…2f96 | Sanctions | Ethereum | 1$0.36 | 0 |
| Tornado Cash 0x12d6…b8fc | Mixer | Ethereum | 3$900 | 0 |
| Stargate 0x53bf…1614 | Bridge | Arbitrum | 0 | 1$1,000 |
| Uniswap v4 0x66a9…a8af | DeFi | Ethereum | 1$3,580 | 1$3,600 |
| Aave v3 0x8787…a4e2 | DeFi | Ethereum | 0 | 1$2,000 |
| Binance 0x28c6…1d60 | Exchange | Ethereum | 1$7,500 | 0 |
| Unidentified 0xbff0…2e24 | Unidentified | Base | 1$2,500 | 0 |
| Unidentified 0x0e85…3eaa | Unidentified | Ethereum | 0 | 1$1,350 |
Number of movements, with their value at current prices.
Activity by network
- First known activity
- 14 Mar 2025
- Latest activity
- 29 Oct 2026
- Balance at current prices
- $6,030
- Active networks
- 3
| Network | Transactions | First activity | Latest activity | Balance |
|---|---|---|---|---|
| Ethereum | 64 | 22 Oct 2026 | 1.84 ETH$5,520 | |
| Arbitrum | 12 | 23 Oct 2026 | 0.05 ETH$150 | |
| Base | 9 | 29 Oct 2026 | 0.12 ETH$360 |
No activity on Polygon, Optimism, Unichain, Avalanche, Scroll, World Chain and Soneium.
Latest transactions
The most recent movements, free with the report.
| Date | Network | Direction | Amount | Value | Counterparty | Transaction |
|---|---|---|---|---|---|---|
| 29 Oct 202609:30 | Base | Sent | 0.12 ETH | $360 | 0x2647…15fb | |
| 27 Oct 202617:45 | Base | Received | 2,500 USDC | $2,500 | 0xbff0…2e24 | |
| 23 Oct 202614:05 | Arbitrum | Received | 0.4 ETH | $1,200 | 0xc505…f310 | |
| 20 Oct 202605:15 | Ethereum | Received | 0.00012 ETH | $0.36 | Lazarus GroupSanctions | |
| 18 Oct 202612:20 | Ethereum | Sent | 0.45 ETH | $1,350 | 0x0e85…3eaa |
8 more movements read are hidden. 85 transactions in total on the networks analysed.
Run it on your own wallets
Create your free account to analyse any address, then import a wallet to get its whole history categorised and ready for your books.
About this analysis
- Recent history only This wallet has more history than what was read: its older transactions are not in the score.
- Unsolicited tokens 3 spam or bait tokens received, left out of the score.
Method and limits
- Direct exposure only: the counterparties that sent funds to this address or received funds from it, one hop away. Funds that went through intermediaries are not traced.
- Shares are measured in US dollars at current prices, separately for what was received and what was sent; without prices, in number of movements.
- Each category of counterparty has a band. A flagged category counts from its first movement and reaches the top of its band at 25% of the volume or more; bridges and DeFi count from 1%. The score is the strongest contribution.
- An address that is itself on a list takes the score of its category.
- Dusting: less than $25 received from a flagged address, with nothing sent back, is a weak signal and never critical.
- Only the latest transactions are read: up to 100 rows per list and per network.
Score bands
- Critical80 to 100
- High60 to 79
- Medium40 to 59
- Low10 to 39
- None0 to 9
Highest level by category
- SanctionsCritical
- HackCritical
- MixerHigh
- Privacy protocolMedium
- BridgeLow
- DeFiLow
- ExchangeNone
Lists used
- OFAC SDN list (U.S. Treasury) 1,011 addresses · issue of 28 Oct 2026 · Source (opens in a new tab)
- OFAC notice lifting the Tornado Cash sanctions 90 addresses · issue of 21 Mar 2025 · Source (opens in a new tab)
- FBI public notice I-022625-PSA on the Bybit hack 51 addresses · issue of 26 Feb 2025 · Source (opens in a new tab)
- Railgun contract addresses published by Railgun 16 addresses · issue of 4 Feb 2026 · Source (opens in a new tab)
- Binance proof of reserves 230 addresses · issue of 1 Nov 2026 · Source (opens in a new tab)
- Protocol contracts recognised by Defi Flow 274 addresses
Not covered
Other sanctions lists (EU, UK, UN), darknet markets, ransomware, scams, hacks and exchanges outside the lists above, indirect exposure beyond one hop, and the networks not listed in this report.
Indicative analysis, computed automatically from public data. It is not a regulated KYT or anti-money-laundering control, and not legal advice. A flag concerns an address, never a person. False positives are possible, and no alert does not mean no risk.
The address is sent to public block explorers to read its history; it is not stored or written to our logs. The report stays in server memory for 10 minutes so it can be displayed again, then it is erased.