| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| JESUS / WETH | uniswap_v2 | 0x8f1b...9068 | 0.0000000221133105700352 |
| JESUS / USDC 1% | uniswap_v3 | 0xa8d0...3dc9 | 0.0000000220188843737549 |
| JESUS / WETH 1% | uniswap_v3 | 0x13da...3841 | 0.0000000220387609987462 |
| BJESUS / JESUS | uniswap_v2 | 0x9d5c...1244 | 0.0000000220372871279218 |
| PepeX / JESUS | uniswap_v2 | 0x887a...3c91 | 0.0000000222711607365545 |
| jesusBLOOD / JESUS 0.01% | uniswap_v3 | 0x724f...7f85 | 0.0000000221586869762606 |
| JESUS / ETH 1% | uniswap-v4-ethereum | 0x2c30...6a96 | 0.00000005400755562 |
| JESUS / WETH 0.3% | uniswap_v3 | 0xa3b2...b469 | 0.0000002094725393 |
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.