| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| CATE / WETH | uniswap_v2 | 0x68d6...1e12 | 0.0000305573444368091 |
| CATE / WETH 1% | uniswap_v3 | 0xbe20...5801 | 0.002571971439 |
| CATE / WETH 0.05% | uniswap_v3 | 0x5ba8...7ccb | 0.00004806925495 |
| CATE / WETH 0.3% | uniswap_v3 | 0x9fab...3924 | 0.0224623300255274 |
| CATE / WBTC 1% | uniswap_v3 | 0xa328...85ac | 0.0167257444200998 |
| CATE / WETH 1% | sushiswap-v3-ethereum | 0xd368...f096 | 0.001657709818 |
| CATE / NEIRO 1% | uniswap_v3 | 0xa22f...944e | 0.0443434808935713 |
| NFAi / CATE | uniswap_v2 | 0x7834...6c75 | 0.0299326337526759 |
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.