Solanaween
The curve completed 40s 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 40s after launch.
noteOnly 2.4 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 20:39 UTC |
| Creator | Eik3RgV2AkkZRPFLeC8QTMtFiJtBajQAW5N93zKmr11Z |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 51 distinct wallets, not counting the creator, bought on the bonding curve: 43 within the first 30s, 7 bundled into the creation block. |
| Graduated | 1 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 | 4XNmFyRBmfHkRJFBsqksXw… slot 451,751,736
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 20:39:34 UTC Slot 451,751,736, which is the chain's own clock for this moment. |
| Creation block | 7 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 43 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-09-29 20:40:14 UTC +40s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 20:40:14 UTC +40s
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. |
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 4 launches from 3 creator wallets, including this one. See them → |
| This creator | 1 earlier launch, 0 confirmed graduated on chain. See the creator's launches → |
| 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 | 2.4 SOL |
| Read from chain | 2026-10-01 03:48 UTC, just now |
What this launch claimed to be
| Name | Solanaween |
| Metadata held | sha256 87bdb5fa524ea6d7b73dc34603def2849eb399660057bb72665147918c346fb0 · 321 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-30 20:40 UTC. |
| Picture held | sha256 8d0b664a27b878d3e862d01d479674aad2abc42c986de605b27faf7187e95fde · 350,984 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 20:39 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.