@lpojqmwrfzxg — ETH address 0x616Ba2…DB3e3F

0x616Ba2c86c5B104D9d54894744C77629D6DB3e3F

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

What we know about this address

ChainEthereum (ETH)
Entity@lpojqmwrfzxg
Categoryindividual
AML score55 / 100 (medium)
Cluster size125 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 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 5 hops from OFAC SDN list (0x76ea76…0412b9).OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x747afb…c5a52b).OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x32da24…f81e3e).OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x95584c…84eae3).OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0x931546…c8c568).OFAC SDN list5inbound
Funds reaching this address are 5 hops from OFAC SDN list (0xdb2720…ada8fe).OFAC SDN list5inbound
Funds reaching this address are 6 hops from OFAC SDN list (0xed6e0a…bad921).OFAC SDN list6inbound

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
sweep-intermediary39.7%
Binance37.2%
Dex Router (OKX)17.1%
unknown4.3%
Gravity Bridge1.8%
OpenSea0.0%

Who it transacts with

CounterpartyKnown asTransactions
0xe7db08292c3aa42b4a2f19f5a5f6dd788e8346e4not attributed55
0x00000000006c3852cbef3e08e8df289169ede581OpenSea22
0x56eddb7aa87536c09ccc2793473599fd21a8b17fBinance10
0x8d53550375c5e3430bbe0081b8bd5f66ea313508Factory8
0xf70da97812cb96acdf810712aa562db8dfa3dbefRelay.link7
0xa5f565650890fba1824ee0f21ebbbf660a179934Relay.link7
0x35b006ae7c4d86cbfcf7a19dfb9ea942163cc86fnot attributed7
0x458a0ec6e49595abbc8596947388d94fa58bd2d3not attributed6

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.