| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| MLN / WETH | uniswap_v2 | 0x15ab...6642 | 4.6179684556069 |
| MLN / USDC 1% | uniswap_v3 | 0x7959...65fa | 16.5324674645 |
| USDC / MLN 1% | uniswap-v4-ethereum | 0x50f6...c71d | 4.68767022447798 |
| USDT / MLN 1% | uniswap-v4-ethereum | 0x8e6a...0727 | 13.0309249591 |
| MLN / WETH | sushiswap | 0x2f8a...48d9 | 4.71906478218477 |
| MLN / WETH 0.3% | uniswap_v3 | 0xd950...77e1 | 11.4079883771 |
| MLN / WETH 1% | uniswap_v3 | 0xbed4...aabc | 53.571223943345 |
| AVA / MLN | uniswap_v2 | 0xae79...6f24 | 4.66326565831968 |
| KABOSU / MLN | uniswap_v2 | 0xf56c...c7e2 | 4.8958247733 |
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.