| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| aETH / WETH | sushiswap | 0x9323...d386 | 2890.9997620158 |
| aETH / ETH 29% | uniswap-v4-ethereum | 0x6d5d...58d7 | 2041.5374005543 |
| aETH / ETH 90% | uniswap-v4-ethereum | 0xc369...34cf | 225.1653872723 |
| aETH / USDC 33% | uniswap-v4-ethereum | 0x9199...7106 | 1624.990338133 |
| aETH / ETH 30% | uniswap-v4-ethereum | 0x4a43...9796 | 2006.0230309178 |
| aETH / WETH | uniswap_v2 | 0x3343...fcb6 | 2634.9494767596 |
| aETH / [invalid] | uniswap_v2 | 0x3d3b...4a0a | 1353.2640838425509050286736188117174752316974440854099700517014405841555861738214541074557227751751817519400619325573311196788 |
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.