0.4%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
233launches carry this ticker, from 174 creator walletsThe curve completed in the same batch of events as the launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
findingIt left the curve 0s after launch.
noteOnly 2.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-11 15:24 UTC |
| Creator | Gjui6jzEvnycDwCrvvYCVSGJJ5Tr6vsxJsMkfZKm8bgm |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 5 within the first 30s, 5 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 0 min after launch |
| Curve on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 9V7rYThRwjorY6mL2hmFXH… slot 446,190,240
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-09-11 15:24:03 UTC Slot 446,190,240, 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. |
| Curve completed | 2026-09-11 15:24:03 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-11 15:24:03 UTC +0s
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. |
| Thirty seconds in | 5 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. |
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 233 launches from 174 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.6% wear one that more than one creator wallet has launched. See this ticker's page → |
Pool
| Liquidity | 2.3 SOL |
| Read from chain | 2026-11-13 09:05 UTC, just now |
What this launch claimed to be
| Name | THE911 |
| Description | Not a monument. Not a reenactment. A dark internet artifact about the signals history leaves behind copied, corrupted, and remembered. |
| Metadata held | sha256 eea448ec465dfc488978ab55b4faa92cd0c76ee112787e5a1e8354bb5cc75499 · 439 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-19 06:24 UTC. |
| Picture held | sha256 48cbbdc6ba35d5529dee1ba28b4fbf307f5f4709e0795697ae7188a20472f01e · 93,871 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-11 15:24 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.