11.4%of supply taken by the creator in the first block
368outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
250launches carry this ticker, from 151 creator wallets2other launches declared this same launch document, byte for byte
2other launches used this exact picture file
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
Also recorded, and not part of the finding above: this picture is on 2 other launches from 2 creator wallets in all. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
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.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-11-12 09:02 UTC |
| Creator | Fx9U91mRL6SgbJftnNQTAeaLPrrDhQKwZeSbkKvN9S4G |
| Creator took | 11.4% of supply in the first block |
| Outside buyers | 368 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: 55 within the first 30s, 10 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 | 58 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 | 5tPw5DyMuXvu6rXzozacYf… slot 468,467,826
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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-11-12 09:02:44 UTC Slot 468,467,826, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 55 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-11-12 10:00:24 UTC +57m 41s 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 3 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 250 launches from 151 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.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 2 other launches, across 2 creator wallets in all. Across the archive, 33.1% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 1 other creator wallet, across 2 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-11-12 15:43 UTC, just now |
What this launch claimed to be
| Name | Shitcoin |
| Metadata held | sha256 2e65b5a211452415d732d6c7c7665acc013dfbf5d81b8b72038d8f70847d99af · 361 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 b27a716f8b33f8f7f2c934302fde319dad39e861cd5871c646627ba80036927a · 19,305 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 09:02 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.