C81
The curve completed 5s 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 5s after launch.
noteOnly 2.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-27 20:58 UTC |
| Creator | 795MWQ2sK5Q8QAwDvYyhmhP6MiJnh2oDa3jC86KdJtav |
| Creator took | 2.0% of supply in the first block |
| Outside buyers | 68 distinct wallets, not counting the creator, bought on the bonding curve: 68 within the first 30s, 16 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 2.1 h ago and it was finished. Checked 2026-09-27 21:02 UTC. |
| Creator sold | not while we watched |
| Recorded from | sn6wPs7n2idcP2AxfsqPSX… slot 451,111,170
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-27 20:58:57 UTC Slot 451,111,170, which is the chain's own clock for this moment. |
| Creation block | 16 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-27 20:59:02 UTC +5s Confirmed against the venue's own completion state. |
| Thirty seconds in | 68 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-27 21:30:28 UTC +31m 31s
1.202e-6 SOL per token.
Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a
decoded one.
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 2 launches from 2 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.8 SOL |
| Read from chain | 2026-09-27 23:10 UTC, just now |
What this launch claimed to be
| Name | C81 |
| Metadata held | sha256 00681c09ff7104d192f828218adccf882ca5bde1c872e29ce30d299f711ad580 · 214 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 6b4ad6421e714c85297a309561417d5cd5c4294a651db1e0ef8fcad710a03eac · 140,986 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-27 20:59 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.