PKG
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
noteThe creator sold while we were watching.
noteOnly 0.2 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 16:38 UTC |
| Creator | 5W2QgyHFofR26DNGpeBjjERGQQCewDoBPTCkE3JUvQW1 |
| Creator took | 0.7% of supply in the first block |
| Outside buyers | 31 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 0 bundled into the creation block. |
| Graduated | 4 min after launch |
| Curve, read 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 | yes |
| Recorded from | oXhaLMWNuniJhihyfKwYJ6… slot 452,343,448
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 16:38:05 UTC Slot 452,343,448, 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-10-01 16:38:19 UTC +14s
9.076e-8 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. |
| Thirty seconds in | 10 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-10-01 16:42:01 UTC +3m 56s 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 | On 22 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 17 launches from 2 creator wallets, including this one. See them → |
| This creator | 133 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 0.2 SOL |
| Read from chain | 2026-10-01 23:07 UTC, just now |
What this launch claimed to be
| Name | parking |
| Metadata held | sha256 8ae5ca26ba7e17150faa862c8bae158b61a9f0fa0c51d873b0f417150b4fe6b9 · 292 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 206d5e825029df1a889ed5cca4f58ac92ecf4f0e9b619d2cecc9a25a04200ba2 · 24,167 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 16:38 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.