LUCK
The curve completed 22s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
findingIt left the curve 22s after launch.
At launch
| Created | 2026-09-30 02:02 UTC |
| Creator | 7zkVun4Kgq4iF17pBCS3tmPkDqc5V59xFwKHoEnyXH8w |
| Creator took | 9.9% of supply in the first block |
| Outside buyers | 150 distinct wallets, not counting the creator, bought on the bonding curve: 150 within the first 30s, 6 bundled into the creation block. |
| Graduated | 0 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 | not while we watched |
| Recorded from | 25LmKj7KV7p8JKGw7TkNCT… slot 451,824,022
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 02:02:20 UTC Slot 451,824,022, which is the chain's own clock for this moment. |
| Creation block | 6 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-30 02:02:42 UTC +22s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 150 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-30 03:14:29 UTC +1h 12m 09s
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. |
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 4 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 49 launches from 35 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 3 other creator wallets, 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 | 40.1 SOL |
| Read from chain | 2026-10-01 10:36 UTC, just now |
What this launch claimed to be
| Name | POTLUCK |
| Metadata held | sha256 dca8297b9e59c5cdc2675f3991b25c2035b24ab5aba67b298177f364389b109e · 250 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-10-01 02:03 UTC. |
| Picture held | sha256 ceb45a1238007504bc4bd6d84b83fcf3b0ed45f6ae78a0091f4704465c31db88 · 216,289 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 02:02 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.