LurkDrop — ETH address 0xDaCAB0…fcd099

0xDaCAB07Cd7713596B6650cC5819FDe284Afcd099

PublicAML knows this Ethereum address as LurkDrop, a CONTRACT. Its AML score is 0 of 100 because we treat this address as infrastructure (known CONTRACT — infrastructure, AML floored). Exposure that reaches it is not scored against it, and the findings below describe what we traced rather than an accusation. Funds reaching this address are 6 hops from OFAC SDN list (0xdcbeff…643193).

What we know about this address

ChainEthereum (ETH)
EntityLurkDrop
CategoryCONTRACT
AML score0 / 100 (floored from 25, treated as infrastructure)
Cluster size1,990,854 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 6 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list6inbound
Funds reaching this address are 6 hops from OFAC SDN list (0x9be599…a15573).OFAC SDN list6inbound
Funds reaching this address are 6 hops from OFAC SDN list (0xed6e0a…bad921).OFAC SDN list6inbound
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 (0x178169…ddd0f1).catalogued mixer3inbound
Funds reaching this address are 3 hops from catalogued mixer (0xd96f2b…364307).catalogued mixer3inbound

3 further internal signals are 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
unknown42.4%

Who it transacts with

CounterpartyKnown asTransactions
0x6d0dc0512bab57e7ea31d03329fc7b7e985dc873not attributed30
0x1cf1aa0d43d7b3af158e6df33ea1005035b17cd3not attributed26
0x821807c8d7a4ee14903a042e280d1ff0f9646a10not attributed16
0xc827d9d694a6ab7b4567fc9380662e5c2ee368f6not attributed16
0x873579df8b3df31615b2a51ceacf7882e4aca67cnot attributed16
0x7b87fbaf44dcc31afa2028eb53227a6833747255not attributed16
0x2d19eb511f34778073a487c87902ee631c59bbc1not attributed12
0x46aa595b29ee6285cf5ae16382a3901ab43157e5not attributed12

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.