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

VRAX67

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

j7gPphMjdmzbAwdESAzY3KKwDTbtNWcivnDqhPQpump Solscan pump.fun
findingIt left the curve 17s after launch.

At launch

Created2026-10-01 02:11 UTC
CreatorDiY1xARmMrtKDtk7EUcaTdTEueJfYz4whDoWWaGan5wg
Creator took0.4% of supply in the first block
Outside buyers39 distinct wallets, not counting the creator, bought on the bonding curve: 39 within the first 30s, 7 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 3.6 h ago and it was finished. Checked 2026-10-01 02:31 UTC.
Creator soldnot while we watched
Recorded from4xmrmK8qfY76fs4gTwkXZF… slot 452,149,053
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-01 02:11:57 UTC
Slot 452,149,053, which is the chain's own clock for this moment.
Creation block7 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-10-01 02:12:14 UTC +17s
Confirmed against the venue's own completion state.
Highest price seen2026-10-01 02:12:14 UTC +17s
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 in39 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 pictureOn 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 2 launches from 2 creator wallets, including this one. See them →
This documentByte-identical to 1 other launch's metadata document. See them →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. 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
NameVRAX67
DescriptionA deadpan blond-cat meme token with black-room energy, silent stare pressure, and the kind of haircut that turns every chart into a mugshot.
Metadata heldsha256 acb69ab135e7350993b558ecdbe2735f0b582f16876a7eb45f6cdeefb3dd5561 · 464 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 8f49239d571704205c38e8fea3831787c161dd50d9ddf1e844f43119536e784a · 254,002 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 02:11 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