loading chain data…
| evidence | ||||
|---|---|---|---|---|
| 0x0163…9a4d | 29d ago | +11% | outcome unavailable | tweet ↗ |
| 0x39db…4571 | 31d ago | +413% | tracked | tweet ↗ |
| 0x232c…30d1 | 31d ago | +0% | rugged | tweet ↗ |
| 0x020b…18b4 | 44d ago | +274% | outcome unavailable | tweet ↗ |
| 0x0366…c041 | 44d ago | — | verifying | tweet ↗ |
| 0xd732…3b88 | 46d ago | +172% | outcome unavailable | tweet ↗ |
| 0x178e…6526 | 50d ago | +17% | outcome unavailable | tweet ↗ |
| 0x4524…fcf9 | 50d ago | +41% | outcome unavailable | tweet ↗ |
| 0xc691…9c31 | 50d ago | +33% | outcome unavailable | tweet ↗ |
| 0xf291…cd03 | 51d ago | +12% | outcome unavailable | tweet ↗ |
source: twitterapi.io · dexscreener · blockscout · updated 8d 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