| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| DF / WETH | uniswap_v2 | 0x2328...1788 | 0.00265889527500442 |
| USX / DF | uniswap_v2 | 0xdae6...ea46 | 0.00265911239357764 |
| USDx / DF | uniswap_v2 | 0xfe73...b3af | 0.00265028825083882 |
| DF / USDC 82.5% | uniswap-v4-ethereum | 0xe483...8bc2 | 0.00278662550097609 |
| DF / USDC 88% | uniswap-v4-ethereum | 0x1f31...a4cb | 0.00281269583015234 |
| DF / WETH | sushiswap | 0xfe66...0c18 | 0.00340686949669887 |
| UTS / DF | uniswap_v2 | 0xa0e7...508d | 0.00392041461364846 |
| DF / KABOSU | uniswap_v2 | 0xdeae...42bc | 0.0112265875 |
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.