| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| UMAD / WETH | uniswap_v2 | 0xd3e5...d8d9 | 0.00000173430773644162 |
| UMAD / DOSE | uniswap_v2 | 0x92bc...8008 | 0.00000174633464725487 |
| UMAD / WETH | sushiswap | 0x0b2f...2bd3 | 0.000002491149096 |
| UMAD / DOSE | sushiswap | 0xe7b3...e34b | 0.00001566322672 |
| UMAD / TOWER | sushiswap | 0xd34e...1aa7 | 0.000005962951899 |
| GMEE / UMAD | sushiswap | 0x7ef4...67a7 | 0.000002554239406 |
| REVV / UMAD | sushiswap | 0xf66f...be1d | 0.00000154398421 |
| LMT / UMAD | sushiswap | 0x5588...97c2 | 0.000003341148932 |
| PROS / UMAD | sushiswap | 0x3b32...bc70 | 0.00000208472325 |
| BONDLY / UMAD | sushiswap | 0xa602...c327 | 0.000001868362053 |
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.