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-04 20:10 UTC |
| Creator | 884kk3pc536WRVsdPeEqCafFaAmCjpYiSzs89da1irBS |
| Creator took | 0.1% of supply in the first block |
| Outside buyers | 5 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, 0 in the very same block the token was created in. |
| Graduated | 2.0 h after launch |
| Curve 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 | 5A9iufi46GmwsfphuMh3HV… slot 444,333,019
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-04 20:10:58 UTC Slot 444,333,019, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Highest price seen | 2026-09-04 20:10:58 UTC
0.000e+0 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. |
| 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-04 22:11:47 UTC +2h 00m 49s Confirmed against the venue's own completion state. |
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. |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | Kirkiversary |
| Description | Celebrating a year to the day Kirk entered AI and birthed a million kirk's |
| Metadata held | sha256 af4abb9df65a214e6de442f403d6cc8144d8ffe653d46909d4ec4c07139595c3 · 374 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-22 14:59 UTC. |
| Picture held | sha256 d41e599c994244816a9dfd076e22f69b03fe3ba7c5d88b1f74021a12ff30606d · 270,332 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-09 19:57 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.