| Name | Related DEX | Address | Token Price (USD) |
|---|---|---|---|
| TRB / ETH 1% | uniswap-v4-ethereum | 0xc6df...656b | 20.8419063367179 |
| TRB / WETH 1% | uniswap_v3 | 0x307c...f206 | 19.7095536560608 |
| TRB / WETH 0.3% | uniswap_v3 | 0x8e40...f757 | 20.3445554692718 |
| TRB / USDT 88% | uniswap-v4-ethereum | 0x7d00...9b5c | 1.92459947158024 |
| TRB / WETH | uniswap_v2 | 0x0928...d987 | 20.4290339224638 |
| TRB / DYDX 1% | uniswap_v3 | 0xbf9b...6969 | 19.9552348553 |
| ADvt / TRB | uniswap_v2 | 0x21e4...cde6 | 22.3656478113 |
| TRB / KABOSU | uniswap_v2 | 0x0e04...097b | 21.272022134 |
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.