| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| ARMOR / WETH | uniswap_v2 | 0x6484...9f6c | 0.000197586610497045 |
| ARMOR / DAI | uniswap_v2 | 0xfc0d...78c7 | 0.000199248347562431 |
| ARMOR / WETH | sushiswap | 0x17a2...109b | 0.000197108088586581 |
| ARMOR / DAI | sushiswap | 0x5a06...8768 | 0.000202904034833702 |
| ARMOR / WBTC | uniswap_v2 | 0x8887...80d9 | 0.000198122446578867 |
| ARMOR / WBTC | sushiswap | 0xcd83...176a | 0.000198388861096864 |
| arNXM / ARMOR | uniswap_v2 | 0x8b09...abf5 | 0.0001986108949 |
| KP3R / ARMOR | sushiswap | 0x9c2e...c5ce | 0.0002106973587 |
| ARMOR / UNI | uniswap_v2 | 0x8afe...8c14 | 0.0002901101242 |
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.