RIVAL
The curve completed 11s 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 11s after launch.
noteOnly 1.4 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 20:31 UTC |
| Creator | 6Qi4KS91Rt1wj8wg9SCi64VSzRzmcJwFhBRTL2tossv6 |
| Creator took | 1.0% of supply in the first block |
| Outside buyers | 104 distinct wallets, not counting the creator, bought on the bonding curve: 104 within the first 30s, 22 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 2.5 h ago and it was finished. Checked 2026-09-30 20:32 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4C2sPsBPtw81XJtSkhmeYE… slot 452,072,722
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 20:31:18 UTC Slot 452,072,722, which is the chain's own clock for this moment. |
| Creation block | 22 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-30 20:31:29 UTC +11s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-30 20:31:29 UTC +11s
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. |
| Thirty seconds in | 104 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. |
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 8 launches from 6 creator wallets, including this one. See them → |
Pool
| Liquidity | 1.4 SOL |
| Read from chain | 2026-09-30 23:03 UTC, just now |
What this launch claimed to be
| Name | Rival |
| Description | Free-entry 1v1 matches. Same clock. Gross closed-trade P&L |
| Metadata held | sha256 c77490b3746b6dc982f08ae4bd6d3cc25733bf51a88881a8a8043777c982aff2 · 316 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 95b13da30f4ff69aecc631e513767d16e663b232503689a8e5d2c4889bbd915c · 172,653 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 20:31 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.