Baby Floki — BSC address 0x71E80e…6dd0c4

0x71E80e96Af604Afc23Ca2AED4C1C7466DB6dd0c4

PublicAML knows this BNB Smart Chain address as Baby Floki, a misc. Our AML risk score for it is 63 of 100, which we read as medium risk. Funds reaching this address are 1 hop from documented incident (0xc62029…999999).

What we know about this address

ChainBNB Smart Chain (BSC)
EntityBaby Floki
Categorymisc
AML score63 / 100 (medium)

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 1 hop from documented incident (0xc62029…999999).0xc620292a45f46a1779244fe4a6a6204ce4999999documented incident1inbound
Funds reaching this address are 1 hop from documented incident (0x82242f…95a586).0x82242f63946c6198ec5bdf765bb013995195a586documented incident1inbound
Funds reaching this address are 8 hops from OFAC SDN list (0x747afb…c5a52b).0x747afb5c7a7fc34b547cd0fdebf9b91759c5a52bOFAC SDN list8inbound
Funds reaching this address are 2 hops from documented incident (0x5322e0…354595).0x5322e0f2c2638343b1cad82638c9dd7c26354595documented incident2inbound
Funds reaching this address are 2 hops from documented incident (0x81a634…4c0fe4).0x81a634ac3427007ebfdbc24620a7ca82724c0fe4documented incident2inbound
Funds reaching this address are 2 hops from documented incident (0xa7ca89…cccc2a).0xa7ca89befad1b33755ef60e1d9a500286ccccc2adocumented incident2inbound
Funds reaching this address are 3 hops from documented incident (0x06569e…8fa3ec).0x06569e99aeee8d1f914914a00dea91ad498fa3ecdocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x4f5714…b78403).0x4f57140f391053b052f5d9b47683b82741b78403documented incident3inbound
Funds reaching this address are 3 hops from documented incident (0xca16d1…8948ab).0xca16d13d5eed95f200426a9fe7a71d52a88948abdocumented incident3inbound
Funds reaching this address are 3 hops from documented incident (0x63605e…c44a51).0x63605e53d422c4f1ac0e01390ac59aaf84c44a51documented incident3inbound

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

See something wrong on this page? Tell us and we will check it.

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.