What this launch shares with other launches
Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for five lists, or with Brand Protection at $79 a month for every list on every record. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.
Its own first blocks
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.
At launch
| Created | 2026-09-10 11:36 UTC |
| Creator | F3zz21goRr8VqeSWp3eEd7DWZs4k4bcjHMpU89kuuKxp |
| Creator took | 4.4% of supply in the first block |
| Outside buyers | 1 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: 4 within the first 30s, 4 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 | 40 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 | yes |
| Recorded from | 2xd6xGgLTBeyasghz8Mftd… slot 445,874,224
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-10 11:36:17 UTC Slot 445,874,224, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 4 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-10 12:16:38 UTC +40m 21s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-10 12:32:16 UTC +56m 00s
6.111e-7 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 1,244 launches from 720 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 → |
Who took the curve
One transaction bought 63 SOL of this curve, 12 min after launch, from a wallet other than the creator's. The wallet and the transaction →
Pool
| Liquidity | 1.1 SOL |
| Read from chain | 2026-11-14 14:31 UTC, just now |
What this launch claimed to be
| Name | KirkIversary |
| Metadata held | sha256 35ca61e7e565cff2deb8b7370a885523efd5f08d711622a009184485d80660df · 162 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-17 14:09 UTC. |
| Picture held | sha256 f7897ecc7de94e7299743a0a114919cbd333acd2fa8213a69fa6540f7c01d4a8 · 28,514 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 11:36 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.