$tupid
The creator took 24% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
noteThe creator took 23.6% of supply at launch.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 20:14 UTC |
| Creator | 5ErKkEaWtgjNXoqY7qGzN73zvjfesDCGD4xbifWECLmB |
| Creator took | 23.6% of supply in the first block |
| Outside buyers | 80 distinct wallets, not counting the creator, bought on the bonding curve: 52 within the first 30s, 3 bundled into the creation block. |
| Graduated | 25 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | yes |
| Recorded from | MD6cDs4pA9P9gUjFcxPhzt… slot 451,746,184
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 20:14:40 UTC Slot 451,746,184, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-09-29 20:14:40 UTC
0.000e+0 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Thirty seconds in | 52 distinct buyers, within the first thirty seconds. A snapshot taken off a tick at the thirty-second mark, so
it carries no moment of its own; it is placed here because that is where it happened. |
| Curve completed | 2026-09-29 20:39:16 UTC +24m 35s Confirmed: a PumpSwap pool was found for it. |
Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.
Seen before
| This picture | On 17 launches from 14 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 31 launches from 24 creator wallets, including this one. See them → |
| This creator | 17 earlier launches, 1 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 4 other creator wallets, across 8 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 07:22 UTC, just now |
What this launch claimed to be
| Name | $tupid money |
| Description | Created on https://rapidlaunch.io |
| Metadata held | sha256 92d03cfea6131d1710dd67a2650206b9687a26290fd064509e21c7e7b78ef35e · 381 bytes Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-30 20:16 UTC. |
| Picture held | sha256 d5fa87ca27a18e483743fb3830adc9e0808fe546d81c5eaa7a929fc38a7f02b7 · 11,438 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 20:14 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.