401K
The curve completed 28s 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 28s after launch.
noteOnly 0.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-19 07:54 UTC |
| Creator | C9mEMMytFtTCZSwSKrJDbVv1mDW92VEBT6JrDtcpojT3 |
| Creator took | 0.9% of supply in the first block |
| Outside buyers | 10 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 1 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 | 4Zis9JwbQb3NVE8RteVNMd… slot 448,345,854
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-19 07:54:37 UTC Slot 448,345,854, 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. |
| Curve completed | 2026-09-19 07:55:05 UTC +28s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-19 07:55:05 UTC +28s
4.109e-7 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. |
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 2 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 69 launches from 56 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 0.8 SOL |
| Read from chain | 2026-09-20 15:16 UTC, just now |
What this launch claimed to be
| Name | 401K |
| Description | Stake your youth. Unlock at 65. |
| Metadata held | sha256 d57bb13cfec5498f77a21b5d003a73a5a935e06d655aec644eb44dc938e0aa09 · 252 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 030b16ecb198178dbcc3306ebc1eee26884361e7f4f208dd63c5cf3d5c909102 · 570,402 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-19 07:54 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.