BASKET
The curve completed 52s 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 52s after launch.
noteOnly 6.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-20 17:48 UTC |
| Creator | 85rbc2D76gzeMGgQMsCEcC1EaNoNtV5pqBPCY7qU9hKP |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 216 distinct wallets, not counting the creator, bought on the bonding curve: 77 within the first 30s, 1 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 | 2Uy1BHNSZonVPNhbEzhroB… slot 448,803,708
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-20 17:48:57 UTC Slot 448,803,708, 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. |
| Thirty seconds in | 77 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-20 17:49:49 UTC +52s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-20 17:49:49 UTC +52s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 72 launches from 52 creator wallets, including this one. See them → |
Pool
| Liquidity | 6.5 SOL |
| Read from chain | 2026-09-22 00:17 UTC, just now |
What this launch claimed to be
| Name | BASKET |
| Description | The whole meta. In a single coin. |
| Metadata held | sha256 9e4cd2ee10cd320a90446ae59341faec53b94a668ed66ad189a723d3b7b9ad54 · 431 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-21 17:49 UTC. |
| Picture held | sha256 d19e7c1e8a2f7abd2394cf84b29c8f5b3527005ba5881b6bffed8cb22af2bd3e · 395,072 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-20 17:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.