loading chain data…
| evidence | ||||
|---|---|---|---|---|
| 0x8d4d…d4dc | 28d ago | +158% | tracked | tweet ↗ |
| 0xeefc…6536 | 28d ago | — | verifying | tweet ↗ |
| 0x49d8…b926 | 40d ago | +0% | tracked | tweet ↗ |
| 0xdbb3…6268 | 41d ago | +0% | outcome unavailable | tweet ↗ |
| 0xd732…3b88 | 41d ago | +566% | outcome unavailable | tweet ↗ |
| 0x4524…fcf9 | 42d ago | +69% | outcome unavailable | tweet ↗ |
| 0xca9c…0edf | 42d ago | +129% | outcome unavailable | tweet ↗ |
| 0x7548…6bd1 | 44d ago | — | verifying | tweet ↗ |
| 0x7912…9ad9 | 44d ago | — | verifying | tweet ↗ |
| 0xf291…cd03 | 45d ago | +6% | outcome unavailable | tweet ↗ |
| 0x020b…18b4 | 49d ago | +257% | outcome unavailable | tweet ↗ |
source: twitterapi.io · dexscreener · blockscout · updated 7d ago · win = +50% still held at the clocked 24h mark (or a current provisional check before that horizon) — a single peak wick is not a win · calls at −50% or worse count against the score · repeat promotion of the same contract counts once (promos column) · handles can change, the underlying twitter id is what's tracked