@leopoldnodde — ETH address 0x1feCb2…F80952
0x1feCb2E6Ed1E930879d86d4734489442f2F80952
PublicAML knows this Ethereum address as @leopoldnodde, a individual. Our AML risk score for it is 70 of 100, which we read as high risk. Funds reaching this address are 3 hops from sanctioned entity (Arkham) (0xfd00b8…3287ba).
What we know about this address
| Chain | Ethereum (ETH) |
| Entity | @leopoldnodde |
| Category | individual |
| AML score | 70 / 100 (high) |
| Cluster size | 419,307 addresses |
Risk findings
Each row is a path our propagation engine traced from a flagged address to this one, with the number of hops and the source that flagged it. A finding is an observation about the flow of funds, not a statement about the owner of this address.
| Finding | Source | Hops | Direction |
|---|---|---|---|
| Funds reaching this address are 3 hops from sanctioned entity (Arkham) (0xfd00b8…3287ba).0xfd00b863fe5b8fd2d95311915d4787452b3287ba | sanctioned entity (Arkham) | 3 | inbound |
| Funds reaching this address are 4 hops from OFAC SDN list (0xdcbeff…643193).0xdcbeffbecce100cce9e4b153c4e15cb885643193 | OFAC SDN list | 4 | inbound |
| Funds reaching this address are 4 hops from sanctioned entity (Arkham) (0x475664…a704f2).0x475664cdedb4ffaf34a81c2a83e2c09417a704f2 | sanctioned entity (Arkham) | 4 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x0c5b44…388f19).0x0c5b4485d96a15e691f77b8b1d7eaee70f388f19 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x09155e…4dbe62).0x09155e8cbb30b34a0fdc65e8419d6c9d684dbe62 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x26538c…ac382f).0x26538ce2b878b022e728fab851ed8beb1eac382f | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0xdc4d51…a25ec5).0xdc4d51d732a7c8e90727eb3628c89ef655a25ec5 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x356956…a99999).0x3569563839c4e308f09122126b4fad3ecaa99999 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x4c0c0c…cca172).0x4c0c0cf65e31baeb7b9cc104ada6658875cca172 | documented incident | 3 | inbound |
| Funds reaching this address are 3 hops from documented incident (0x68f5e0…62231d).0x68f5e08784d6e0725051c8850c016372fb62231d | documented incident | 3 | inbound |
If this page is wrong
Attribution and risk propagation both make mistakes, and a page like this one is visible for a long time. If you own this address or can show that a finding here is incorrect, tell us and we will re-check it. Corrections are applied to the underlying data, so they carry over to the API and to every other view of this address.
See something wrong on this page? Tell us and we will check it.
PublicAML reports what it can observe on-chain and what public and vendor sources say about an address. Nothing on this page is a legal finding, an allegation against a person, or advice. Risk scores describe exposure through transaction paths, and an address can carry exposure without its owner having done anything wrong.
Data is read live from the PublicAML API at the time this page was served.