Also recorded, and not part of the finding above: this creator has 4 other launches on record. 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. They are listed under Seen before, further down this page.
At launch
| Created | 2026-09-06 20:23 UTC |
| Creator | HqoXeF2CnsPCC63xGqmv3ESDLPDC2muKjGb3Ejo4kW51 |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 37 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: 16 within the first 30s, 0 in the very same block the token was created in. |
| 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 | 4SE14UaWoF12qrFijQjLsp… slot 444,882,664
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-06 20:23:39 UTC Slot 444,882,664, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 16 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-09-06 20:25:21 UTC +1m 41s
4.892e-8 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 136 launches from 113 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 creator | 4 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.6% of launches come from a creator with more than one launch on record. See the creator's launches → |
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 | MOONCAP |
| Description | A moon-bound mushie with diamond hands, calm vibes, and enough liquidity drip to survive even the nastiest dump. |
| Metadata held | sha256 608257d17c4c1326ff115f763c9e04165837ee5e0f4d8b8c347a1f43ae5b2207 · 405 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 4f6bd571483cd96387bea4cb1e892775cc576a2c712669cb694d2ddfa115f902 · 475,059 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 19:41 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.