AMD
The curve completed in the same batch of events as the 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.
findingOnly 4 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 1.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-25 15:01 UTC |
| Creator | 44Afa84mXeAPJgLrqSE3UqAa15SB8ECnJJ3DVq1pVQ5d |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 4 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 4 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 | 2nCtMArBgR2CKN6ksVxYhf… slot 450,387,042
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-25 15:01:40 UTC Slot 450,387,042, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-25 15:01:40 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 4 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-25 15:09:16 UTC +7m 35s
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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 488 launches from 362 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 3 creator wallets. See the linked wallets → |
Pool
| Liquidity | 1.7 SOL |
| Read from chain | 2026-09-26 19:47 UTC, just now |
What this launch claimed to be
| Name | All Meme Days |
| Description | From now on, every day is Meme Day，conform to the narrative nowadays. |
| Metadata held | sha256 01ff6aaeb3ed60177b513dfaca5f8fa43a75c6496a248db96ebac6691025d279 · 382 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-09-26 15:02 UTC. |
| Picture held | sha256 25813fd34303afe775aa53a32ac003a0ddc6f0538b0e73ce6d5215b445fcd3b1 · 117,194 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-25 15:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.