| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| LRT2 / ETH 1% | uniswap-v4-ethereum | 0x65d3...a29f | 145.8599842291 |
| LRT2 / WETH 1% | uniswap_v3 | 0x2956...1d66 | 144.5954239248 |
| LRT2 / ETH 0.3% | uniswap-v4-ethereum | 0x26f7...235e | 257.3990245584 |
| UDS / LRT2 5% | uniswap-v4-ethereum | 0x22a3...d3f3 | 135.552961103028 |
| LRT2 / WETH 0.25% | pancakeswap-v3-ethereum | 0x38be...bce6 | 235.6786915642 |
| USDCc / LRT2 99.111% | uniswap-v4-ethereum | 0x281c...2420 | 158.067551438368 |
| LRT2 / ETH 1% | uniswap-v4-ethereum | 0x1caf...d533 | 1936.0727233322 |
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.