| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| PEPE2.0 / WETH | uniswap_v2 | 0x076a...a269 | 0.0000000000810140487680336 |
| PEPE2.0 / WETH 1% | uniswap_v3 | 0xd738...b6f8 | 0.0000000000794850124855467 |
| PEPE2.0 / WETH 0.3% | uniswap_v3 | 0xf09e...4695 | 0.000000062900588138814 |
| PEPE2.0 / WETH | x7-finance | 0x2e78...8c7d | 0.0000000208704539804061 |
| PEPES / PEPE2.0 1% | uniswap_v3 | 0xf061...06fc | 0.0000000442023247836714 |
| PEPES / PEPE2.0 0.01% | uniswap_v3 | 0x7a07...9930 | 0.000000051483936696087 |
| DOGE2.0 / PEPE2.0 | uniswap_v2 | 0x0e9e...83f9 | 0.0000000296308792785326 |
| PEPE / PEPE2.0 1% | uniswap_v3 | 0xe956...d169 | 0.0000000100508590698169 |
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.