7
The creator took 40% 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 39.5% of supply at launch.
At launch
| Created | 2026-09-30 03:47 UTC |
| Creator | FSD1aWi9ZhkNWbDrgk4ckXDXmr7eET2oHJzaTefqCbsP |
| Creator took | 39.5% of supply in the first block |
| Outside buyers | 808 distinct wallets, not counting the creator, bought on the bonding curve: 109 within the first 30s, 5 bundled into the creation block. |
| Graduated | 14.1 h 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 | not while we watched |
| Recorded from | 27BjpmZZFPLfM9zphGVkZA… slot 451,847,604
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 03:47:24 UTC Slot 451,847,604, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 109 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-30 17:55:09 UTC +14h 07m 45s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 17:55:09 UTC +14h 07m 45s
4.109e-7 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. |
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 | No other launch we hold a picture for used this one. |
| This ticker | On 328 launches from 240 creator wallets, including this one. See them → |
Pool
| Liquidity | 61.1 SOL |
| Read from chain | 2026-09-30 23:36 UTC, just now |
What this launch claimed to be
| Name | Cornell |
| Description | This story about seven Cornell students accused of drugging and gang raping a woman is going insanely viral. |
| Metadata held | sha256 7070a32bd3a3e369083c47da891aa2d50f95b187926553ffb9c1d0c355b707e9 · 522 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. |
| Picture held | sha256 648001891e23211fdefc60524c8dd46c09cac085a59afad58668c019cd5eea82 · 530,926 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 03:47 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.