loading chain data…
showing the newest 500 calls; the aggregate score uses the full-history agent cache when that cache is current
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