| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| QKC / WETH | dodo-pmm-ethereum | 0x4705...bfc5 | 0.002658095405 |
| QKC / ETH 50% | uniswap-v4-ethereum | 0xfb9e...3221 | 0.00351201809 |
| QKC / WETH | dodo-pmm-ethereum | 0x888f...2149 | 0.003283607104 |
| USDC / QKC 24.88% | uniswap-v4-ethereum | 0x65ff...52b5 | 0.0035557790206865 |
| USDC / QKC 9.88% | uniswap-v4-ethereum | 0x5685...757a | 0.005261362288 |
| QKC / WETH | uniswap_v2 | 0xb05d...150d | 0.002934024512 |
| QKC / WETH 1% | uniswap_v3 | 0xfa13...7250 | 0.007016955365 |
| KABOSU / QKC | uniswap_v2 | 0x3448...6338 | 0.00403186608 |
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.