1,190,800 launches on record
Coverage from 2 Sep 2026
Archive read 21:03 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

$ZYVR

The curve completed 20s 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.

CX3B3eWB3jXM82bPn4mST2oGMs6JmRDPacB4uHXrpump Solscan pump.fun
findingIt left the curve 20s after launch.

At launch

Created2026-10-01 16:21 UTC
CreatorDprXRa7JkEEfHHmmpNsVAi3HSq9oeFbCiLXjSGZVtoQj
Creator took0.2% of supply in the first block
Outside buyers32 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 0 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 5.0 h ago and it was finished. Checked 2026-10-01 18:01 UTC.
Creator soldnot while we watched
Recorded from2qVtHgJCDi2rL9aTHJrhNq… slot 452,339,845
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-01 16:21:50 UTC
Slot 452,339,845, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-10-01 16:22:10 UTC +20s
Confirmed against the venue's own completion state.
Highest price seen2026-10-01 16:22:17 UTC +27s
2.289e-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 in5 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 pictureNo other launch we hold a picture for used this one.
This creator4 earlier launches, 0 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets →

Pool

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
NameZyvron
Description Zero hype. Pure meme.
Metadata heldsha256 cdda70f10a9ccfa5678ca6dc723d4f01ce9a9847ae37d7516545a2650a0362c4 · 216 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 heldsha256 38676c6d24d317649f21b737242a1ade3798920f719e433fbf0a17c50a816f0f · 182,959 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 16:21 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another