@KingDragonNFT — ETH address 0xdD607c…101dF6

0xdD607c06D862260C4eC7A155a8E310ee46101dF6

PublicAML knows this Ethereum address as @KingDragonNFT, a individual. Our AML risk score for it is 55 of 100, which we read as medium risk. Funds reaching this address are 4 hops from sanctioned entity (Arkham) (0x475664…a704f2).

What we know about this address

ChainEthereum (ETH)
Entity@KingDragonNFT
Categoryindividual
AML score55 / 100 (medium)
Cluster size68 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.

FindingSourceHopsDirection
Funds reaching this address are 4 hops from sanctioned entity (Arkham) (0x475664…a704f2).sanctioned entity (Arkham)4inbound
Funds reaching this address are 5 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x5a7a51…a3b59f).OFAC SDN list5inbound
Funds reaching this address are 3 hops from catalogued mixer (0xd4b88d…c8cfa3).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0x4736dc…cfba9d).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0xfd8610…6c7144).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0x23773e…f25334).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0x610b71…5ceab4).catalogued mixer3inbound

1 further internal signal is held back from this page. They come from heuristics with known false positives, and we do not publish an accusation we would not defend. They are visible in the live check.

Where the funds came from

SourceShare of received value
Nexo37.5%
Circle36.6%
BloctoApp14.8%
unknown10.4%
OpenSea0.3%
WETH0.1%
@KingDragonNFT0.0%

Who it transacts with

CounterpartyKnown asTransactions
0x00000000006c3852cbef3e08e8df289169ede581OpenSea408
0x44c9ff8343bdf35d3b84321b1a6bbb617216a287not attributed187
0x7f268357a8c2552623316e2562d90e642bb538e5OpenSea166
0x0000a26b00c1f0df003000390027140000faa719OpenSea165
0x54ee6bec471fd8cfd2354d702e43c1311dc9683bnot attributed149
0xf6045e92121a4aac74320e038258e0fe0d537cb5not attributed140
0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2WETH99
0x000000000000ad05ccc4f10045630fb830b95127Blur59

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.

Contact us about 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.