| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| QUA / DAI | sushiswap | 0x4cee...4a4c | 0.000209317515751338 |
| QUA / USDT 0.3% | balancer_ethereum | 0x3f72...8834 | 0.000206756129327295 |
| QUA / DAI 0.3% | uniswap_v3 | 0xabb6...3809 | 0.0005860672593 |
| QUA / DAI | uniswap_v2 | 0x60ec...9d1f | 0.0002153209396 |
| QUA / USDT 0.01% | pancakeswap-v3-ethereum | 0xb336...aa74 | 0.001693245608 |
| QUA / USDT | smardex-ethereum | 0xfa79...3192 | 0.0001941770823 |
| USDT / QUA | curve | 0x6d6e...007c | 0.0001929027498 |
| QUA / USDT 0.1% | maverick-v2-eth | 0x66f8...78e1 | 0.0005430737016 |
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.