| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| MTA / WETH | uniswap_v2 | 0x0d0d...0455 | 0.030440461273722 |
| MTA / WETH 0.3% | uniswap_v3 | 0xa96c...9dbb | 0.0317244375536044 |
| MTA / WETH 0.41% | balancer_ethereum | 0xe246...1c49 | 0.0319485898997565 |
| MTA / WETH | sushiswap | 0x6632...b9a0 | 0.0322761695950768 |
| MTA / WETH | defi_swap | 0x47a6...523a | 0.03259892963 |
| CRO / MTA | defi_swap | 0x0b67...c2d4 | 0.03043163524 |
| MTA / DAI | uniswap_v2 | 0x53b2...16a6 | 0.03869998514 |
| Seal / MTA | uniswap_v2 | 0x256e...36f4 | 0.03180315244 |
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.