Also recorded, and not part of the finding above: this picture is on 13 other launches from 13 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.4% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
At launch
| Created | 2026-09-15 14:03 UTC |
| Creator | 463F9vREXxV3zvrx5z7UT8CrRR4xc81YSRGyFTeAhmWR |
| Creator took | 4.7% 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: 2 within the first 30s, 1 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 | not while we were watching |
| Curve on chain | Nothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them. |
| Creator sold | not while we watched |
| Recorded from | 66d2gtKYjcdjBnp7FbdaCP… slot 447,268,131
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-15 14:03:45 UTC Slot 447,268,131, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 2 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. |
| Highest price seen | 2026-11-12 22:52:52 UTC +58d 08h
0.000e+0 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 | On 14 launches from 13 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.4% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 91 launches from 74 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
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 | JACKAT |
| Metadata held | sha256 54b7dbd6e4a1e87e0d67a2d2778d32d4545a2ed7d41df4ee2475fbe304a9a782 · 294 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 dc534096f669e408d6c1176ae331187e6a7e90ed3631cf6ee7a6477c3f57d2e4 · 20,852 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-15 14:03 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.