| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| LM / ETH 85% | uniswap-v4-ethereum | 0xb9c3...d87f | 0.02056990949 |
| LM / USDT 99.99% | uniswap-v4-ethereum | 0x0309...c413 | 0.0001323499919 |
| LM / USDT 89% | uniswap-v4-ethereum | 0xb63c...4170 | 0.0001205047582 |
| USDC / LM 98% | uniswap-v4-ethereum | 0xde14...2394 | 0.0001299610378 |
| LM / USDT 88% | uniswap-v4-ethereum | 0x2f0b...0806 | 0.00009699605485 |
| LM / ETH 30% | uniswap-v4-ethereum | 0x139d...83ba | 0.000791670469927345 |
| LM / USDT 90% | uniswap-v4-ethereum | 0x32b4...3c85 | 0.00007826387922 |
| LM / USDT 99.9% | uniswap-v4-ethereum | 0x3797...08da | 0.0001211577807 |
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.