$cum
The curve completed 19s 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 19s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 14:25 UTC |
| Creator | FFfL3deSpLwipFvCD5EKrzvrYLbpa4h8U8zvqRMwzirn |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 25 distinct wallets, not counting the creator, bought on the bonding curve: 1 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 5.1 h ago and it was finished. Checked 2026-09-30 14:32 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4ZFKeF83nB11YqrNALrC6X… slot 451,990,809
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 14:25:11 UTC Slot 451,990,809, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-30 14:25:30 UTC +19s Confirmed against the venue's own completion state. |
| Thirty seconds in | 1 distinct buyer, 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-30 14:25:59 UTC +48s
2.936e-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. |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-09-30 19:40 UTC, just now |
What this launch claimed to be
| Name | cum |
| Description | cum |
| Metadata held | sha256 f81db5e0e7773efff47f7419bc4ff6d7fabd207876a65fb08f2b3e993408cfd9 · 188 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 cc2ccf0bf4d82c6d3c20502399c9f7a2511e57674ce43061c25c32041ec0b429 · 22,106 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 14:25 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.