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-11-07 08:29 UTC |
| Creator | GpTdbMsNutXmYZXdtwLnpcktddDEFFFJimNzDNaNFjPz |
| Creator took | 79.3% of supply in the first block |
| Outside buyers | 0 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: 0 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | yes; we did not record when |
| 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 | 4CDVarzgGLRRXTd6yvDUEy… slot 466,445,500
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-07 08:29:43 UTC Slot 466,445,500, 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 | No buyer, 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-07 08:41:40 UTC +11m 57s
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. |
| Curve completed | Recorded as complete; we did not record when.
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 | No other launch we hold a picture for used this one. |
| This ticker | On 1,011 launches from 558 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 → |
Who took the curve
One transaction bought 85 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
Pool
| Liquidity | 2.0 SOL |
| Read from chain | 2026-11-12 11:00 UTC, just now |
What this launch claimed to be
| Name | dont ignore this kitten |
| Metadata held | sha256 0a568938a166d5ae32ea445a49187d48826cb1f1006103a0b499c0da949e7360 · 244 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-11-10 00:26 UTC. |
| Picture held | sha256 7835465237eb1b69a4279218954ed140f85cdf8ac4e1e4a9cd2b6e34ff25bbdf · 33,993 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-07 08:29 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.