| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| TOKE / WETH | sushiswap | 0xd4e7...7e38 | 0.04800403537 |
| AUTO / TOKE | curve | 0x9085...5854 | 0.0477411559754402 |
| TOKE / WETH | uniswap_v2 | 0x5fa4...c688 | 0.04911233141 |
| TOKE / WETH | curve | 0xe0e9...ba7f | 0.04965391974 |
| TOKE / WETH 0.3% | uniswap_v3 | 0x3b33...d6fb | 1.1436647206 |
| TOKE / WETH 1% | uniswap_v3 | 0x500c...07b6 | 0.991577012753809 |
| TOKE / ETH 0.3% | uniswap-v4-ethereum | 0x65a9...2b50 | 0.05206630414 |
| TOKE / SUSHI | sushiswap | 0x6496...8ebe | 0.05755690874 |
| TOKE / USDC 0.25% | pancakeswap-v3-ethereum | 0x1830...919b | 0.2034233805 |
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.