@lovewassie — ETH address 0x4f23f9…1cc4F7

0x4f23f946562D26f62a80C06b4a6909dA371cc4F7

PublicAML knows this Ethereum address as @lovewassie, 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 OFAC SDN list (0xdcbeff…643193).

What we know about this address

ChainEthereum (ETH)
Entity@lovewassie
Categoryindividual
AML score70 / 100 (high)
Cluster size271 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 3 hops from OFAC SDN list (0xdcbeff…643193).OFAC SDN list3inbound
Funds reaching this address are 4 hops from OFAC SDN list (0x9be599…a15573).OFAC SDN list4inbound
Funds reaching this address are 4 hops from OFAC SDN list (0xf2235d…2e27cb).OFAC SDN list4inbound
Funds reaching this address are 4 hops from sanctioned entity (Arkham) (0x475664…a704f2).sanctioned entity (Arkham)4inbound

6 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
Kyber Network100.0%
unknown0.0%
MetaMask0.0%
BlockFi0.0%
Kraken0.0%
Synapse Protocol0.0%
Avalanche0.0%

Who it transacts with

CounterpartyKnown asTransactions
0x7be8076f4ea4a4ad08075c2508e481d6c946d12bOpenSea1165
0x7f268357a8c2552623316e2562d90e642bb538e5OpenSea265
0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2WETH250
0x88332c505d014b22f7e817d74c68079c75457e04not attributed169
0x1d34d469d1a5dced6416eb22d0125bd3cca9436bnot attributed133
0x00000000006c3852cbef3e08e8df289169ede581OpenSea130
0x000000000000ad05ccc4f10045630fb830b95127Blur105
0xb6f38280e36f6efacdb535e539a95c391b26047bnot attributed93

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.