| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| moSOLID / WETH | solidlydex | 0xf5e4...de8a | 0.00286951993659925 |
| moSOLID / USDC | solidlydex | 0x10f5...b7e3 | 0.00315724231715576 |
| moSOLID / WETH 1% | uniswap_v3 | 0x9908...232f | 0.315628355388284 |
| moSOLID / USDC 1% | uniswap_v3 | 0xac60...af81 | 0.210428878029166758409130699608 |
| moSOLID / WETH | solidlydex | 0xe40c...c7bd | 0.008111703866 |
| SOLID / moSOLID 1% | uniswap_v3 | 0x91ca...9fc0 | 0.311302161998415282402531872524 |
| moSOLID / USDC | solidlydex | 0x0544...c7fb | 0.583629519139339568693078260134 |
| moSOLID / WETH | uniswap_v2 | 0x3b30...3289 | 0.000000000003702443841 |
| SOLID / moSOLID | solidlydex | 0x96f2...0924 | 0.439422437461029721464352643784 |
| fBOMB / moSOLID | solidlydex | 0x1681...383a | 0.004007563897 |
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.