Name | Related DEX | Address | Token Price (USD) |
---|---|---|---|
AGRS / WETH 1% | uniswap_v3 | 0xaddd...73a3 | 0.596819327065266 |
AGRS / USDT 1% | uniswap_v3 | 0xb77a...d0a9 | 1.6389368628 |
AGRS / ETH 1% | uniswap-v4-ethereum | 0xbf4e...4a4e | 0.9621179395 |
AGRS / USDT 1% | uniswap-v4-ethereum | 0x3381...4be1 | 0.9034614055 |
eMAID / AGRS 1% | uniswap_v3 | 0x9c2f...b4c9 | 0.7568140881 |
AGRS / WETH | uniswap_v2 | 0xd89f...3c7d | 0.6819987519 |
AGRS / USDT 0.3% | uniswap_v3 | 0xa1b0...717d | 4.22365046572704 |
eMAID / AGRS | uniswap_v2 | 0x549c...615a | 2.35144751304793 |
AGRS / KABOSU | uniswap_v2 | 0x1f65...1bce | 0.8246039098 |
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.