0x0E5a32139b0e5bB4eC0154674625bF342ef8CED5
PublicAML knows this Ethereum address as mintTokenwithPoolCreation, a TOKEN. Its AML score is 0 of 100: we found nothing to report against it. Funds reaching this address are 3 hops from catalogued mixer (0x91f69f…3c80cf).
| Chain | Ethereum (ETH) |
| Entity | mintTokenwithPoolCreation |
| Category | TOKEN |
| AML score | 0 / 100 (low) |
| Cluster size | 1,206,009 addresses |
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 catalogued mixer (0x91f69f…3c80cf). | catalogued mixer | 3 | inbound |
| Source | Share of received value |
|---|---|
| unknown | 41.7% |
| sweep-intermediary | 6.3% |
| Counterparty | Known as | Transactions |
|---|---|---|
| 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 | WETH | 14 |
| 0x702003461ac2f025fb4f88e25e03ee45b7adfad9 | not attributed | 7 |
| 0xb02d877f22fc84087be901bd8fa18e780b15e198 | not attributed | 6 |
| 0xdd09d19aa09279ff2e5ddb270355dd0c33602706 | not attributed | 6 |
| 0x03ee7b2044f732f0b413ce01b93bf3296bfa8321 | not attributed | 4 |
| 0x061ed36d0d3c96e9a3e5811c76d1d10c8bc3b8b7 | not attributed | 4 |
| 0x136fef1c0b88b5e226b169d237568373369e8866 | not attributed | 4 |
| 0x14520af38c5a8423cd61f9861dac27d2f1484a62 | not attributed | 4 |
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.
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.