| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| ROOT / KETH | uniswap_v2 | 0x44ee...1d46 | 1215.6588662888 |
| ROOT / WETH | uniswap_v2 | 0x01f8...2c33 | 1397.8764500279 |
| RLP:WETH / ROOT | uniswap_v2 | 0x283c...d657 | 1320.3825320501 |
| ROOT / RLP:KETH | uniswap_v2 | 0x318b...b095 | 1498.3214078126 |
| KETH / ROOT | sushiswap | 0x04c7...ab9e | 1426.445279384358302226690186342598447927882774844304409689290405702616410071993461937446348 |
| PROPHET / ROOT | uniswap_v2 | 0x9ec1...ea66 | 1617.652104932 |
| DEFLCT / ROOT | uniswap_v2 | 0xbbc0...e32a | 1029.750952381 |
| RK:ETH / ROOT | uniswap_v2 | 0x0617...46f6 | 1543.2343802404 |
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.