| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| SERV / WETH 1% | uniswap_v3 | 0x9c7e...fcbb | 0.0207590229113001 |
| SERV / WETH | uniswap_v2 | 0xb771...600e | 0.0205952413711601 |
| SERV / ETH 1% | uniswap-v4-ethereum | 0x2b25...8094 | 0.0198712878009578 |
| SERV / USDC 0.3% | uniswap-v4-ethereum | 0x61dc...a305 | 0.08503340696 |
| SERV / USDC 80% | uniswap-v4-ethereum | 0xd430...bf83 | 0.1381051688 |
| SERV / USDC 0.3% | uniswap_v3 | 0xcdeb...1c28 | 0.04256083168 |
| SERV / USDT 0.3% | uniswap_v3 | 0xba1b...8ca2 | 0.04133167465 |
| SERV / USDT 0.3% | uniswap-v4-ethereum | 0x21d7...c037 | 0.0418430855 |
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.