| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| MX / WETH | uniswap_v2 | 0xdf4a...8f5b | 2.06853000141684 |
| MX / ZIK 1% | uniswap-v4-ethereum | 0x8f32...1911 | 2.1374208583326 |
| MX / TOM3 0.3% | uniswap_v3 | 0x3e2d...ce94 | 2.04517825535825 |
| MX / USDT 50% | uniswap-v4-ethereum | 0x886d...f4c0 | 1.1890904868 |
| MX / ETH 10% | uniswap-v4-ethereum | 0xa8d5...ab48 | 2.13176233733988 |
| MX / USDT | uniswap_v2 | 0x1af1...5710 | 2.5633679344 |
| MX / WETH 1% | uniswap_v3 | 0x4522...78f9 | 2.7022780961 |
| MX / USDC 1% | uniswap_v3 | 0x5461...bf04 | 2.97581360074146 |
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.