| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| FLEX / USDC | uniswap_v2 | 0x3f61...e820 | 0.1429526778 |
| FLEX / WETH 1% | uniswap_v3 | 0xfe5c...9919 | 1.621950293 |
| FLEX / USDT | sushiswap | 0x203b...1806 | 0.142815808 |
| FLEX / USDC 1% | uniswap_v3 | 0x187a...9526 | 1.24489878328149 |
| FLEX / USDC 0.3% | uniswap_v3 | 0xb552...ebf1 | 0.913976331896277099985143947345 |
| OX / FLEX 1% | uniswap_v3 | 0x82cb...fe8d | 0.549677881299453 |
| FLEX / WETH 0.3% | uniswap_v3 | 0x932a...6877 | 3.30809991205692 |
| FLEX / USDT 0.3% | uniswap_v3 | 0x74e1...05bd | 1.36472091040151723695021901695 |
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.