Name | Related DEX | Address | Token Price (USD) |
---|---|---|---|
ACH / WETH 1% | uniswap_v3 | 0xeb46...95fb | 0.0250669190258558 |
ACH / WETH | uniswap_v2 | 0xc645...b6fa | 0.0245382755160296 |
ACH / USDT 1% | uniswap_v3 | 0xbe3c...ab38 | 0.04498212498 |
ACH / WBTC 1% | uniswap_v3 | 0x2532...7c65 | 0.0294269307024417 |
ACH / USDC | sushiswap | 0x5c14...7ce6 | 0.03385939089 |
ACH / WBTC | sushiswap | 0x2e63...be38 | 0.01145122678 |
ACH / USDC 0.3% | uniswap_v3 | 0xee54...b037 | 0.039514344852497919516191495625 |
ACH / USDT | sushiswap | 0x4ffe...3f83 | 0.03475764066 |
KABOSU / ACH | uniswap_v2 | 0x21c0...1569 | 0.02449934152 |
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.