| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| KCT / USDC 93% | uniswap-v4-ethereum | 0x3174...0e48 | 0.00005455885097 |
| KCT / USDC 90% | uniswap-v4-ethereum | 0x577e...4299 | 0.07031810975 |
| KCT / ETH 95% | uniswap-v4-ethereum | 0xee9a...48f3 | 0.01703446589 |
| KCT / USDC 90% | uniswap-v4-ethereum | 0x44ee...37d8 | 0.001404484349 |
| KCT / USDC 90.001% | uniswap-v4-ethereum | 0x833f...97f8 | 0.08504151941 |
| KCT / USDT 0.25% | pancakeswap-v3-ethereum | 0xbf3b...30f3 | 1242.7305173428 |
| KCT / USDC 81.6% | uniswap-v4-ethereum | 0x70b7...1801 | 0.0002403588715 |
| KCT / USDT 0.05% | uniswap-v4-ethereum | 0xed99...e3fe | 0.0008031524049 |
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.