| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| BABYPEPE / WETH | uniswap_v2 | 0x5b6a...fe44 | 0.0000000000344330804197808 |
| BABYPEPE / WETH 1% | uniswap_v3 | 0xbc38...1981 | 0.0000000001613083464 |
| BABYPEPE / SPANK | curve | 0x6053...28e3 | 0.00000000003556769797 |
| SPANK / BABYPEPE | curve | 0xb3b0...5f1c | 0.0000000000339611388054834 |
| BABYPEPE / SPANK 1% | pancakeswap-v3-ethereum | 0x9a5b...5b2b | 0.0000000000792751545010921 |
| BABYPEPE / SPANK | sushiswap | 0x691b...b735 | 0.0000000000863828725905765 |
| BABYPEPE / NIGGER 1% | uniswap_v3 | 0x3ee7...1f01 | 0.00000000002791523793 |
| Illiterate / BABYPEPE 1% | uniswap_v3 | 0x449c...419d | 0.000000000118812891572969 |
Generally, a honeypot Detector operation consists of a computer, applications and data that simulate the behavior of a real system that would be attractive to attackers, such as a financial system, internet of things (IoT) devices, or a public utility or transportation network. It appears as part of a network but is actually isolated and closely monitored. Because there is no reason for legitimate users to access a honeypot, any attempts to communicate with it are considered hostile.