Robinhood Chain · chainId 4663 · deployer record
0x36aa…4f323 launches
This wallet has launched 3 tokens on Robinhood Chain, and 2 of them carry the same ticker — $BLAST. The first we hold is dated and the most recent .
2 of them are called $BLAST. The same name launched over again leaves the earlier ones behind by construction: whoever bought those is holding the ones that did not catch.
0 of the 3 still hold at least $1,000 of liquidity, and 1 carry a HIGH or CRITICAL structural finding from our scan. Several launches is not evidence of anything on its own — this is the record, not a verdict.
0x36aa2f98ed44755172ca8d1440d2fbaa6f5d4f32Every token this wallet launched
| Token | Launched | Liquidity | Our scan |
|---|---|---|---|
| 0xd6a1…ac26 | — | not scanned | |
| $BLAST | first seen | — | HIGH structural risk |
| $BLAST | first seen | — | MEDIUM structural risk |
How to read this
A launch count is a fact, not a finding. What makes a record worth reading is the shape of it: the same ticker launched twice is one operator spraying a name until one catches; a dozen launches in an hour is tooling, not a project; a wallet whose earlier tokens all still trade is a different story from one whose earlier tokens are all at zero. The scans linked above hold the evidence behind each — a clean read is evidence, not a recommendation.
Cite this
PumpPill, “Robinhood Chain deployer record: 0x36aa…4f32”, as of 2026-10-01 (UTC). https://www.pumppill.org/rh/deployer/0x36aa2f98ed44755172ca8d1440d2fbaa6f5d4f32
Built from PumpPill’s own index of Robinhood Chain (chainId 4663): the launchpad event log and every token we have indexed, joined to our stored scans. Counts only — we do not publish a win rate, because a record of tokens that crossed a level has no losers in the denominator.