3,511,014 launches on record
Coverage from 2 Sep 2026
Archive read 06:31 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection
The picture this launch published at birth

Launch record · observed at creation 2026-11-12 01:02 UTC

ELONMAX

Elon Max

CHJdhATLqmbDPU6NkbhHqoaVjGYusB9xFfduFpPBpump Solscan pump.fun
0.2%of supply taken by the creator in the first block
17outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
8launches carry this ticker, from 8 creator wallets
2other launches declared this same launch document, byte for byte
2other launches used this exact picture file
The curve completed 4s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

Also recorded, and not part of the finding above: this picture is on 2 other launches from 3 creator wallets in all. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

findingIt left the curve 4s after launch.

At launch

Created2026-11-12 01:02 UTC
Creator33GuBDChEzk5xrNh8AbsVjtuJTzZL8PoZcwWbdddjbCY
Creator took0.2% of supply in the first block
Outside buyers17 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 17 within the first 30s, 17 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 6.6 h ago and it was finished. Checked 2026-11-12 01:30 UTC.
Creator soldnot while we watched
Recorded from5etvQRBAaMfqeE2ZVMt3Pb… slot 468,333,805
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

Order of events

Created2026-11-12 01:02:36 UTC
Slot 468,333,805, which is the chain's own clock for this moment.
Creation block17 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-11-12 01:02:40 UTC +4s
Confirmed against the venue's own completion state.
Thirty seconds in17 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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 8 launches from 8 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.5% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 2 other launches, across 3 creator wallets in all. Across the archive, 33.1% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, across 3 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group of 3 creator wallets in all. Across the archive, 63.9% of launches come from a creator linked to at least one other wallet this way. 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
NameElon Max
Metadata heldsha256 f8e692a8e9f052c1501c5c25cd5eba654ae5b482e1b5e16124b64e0208a2de25 · 304 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 74b36e7d77ff7d6a724052d7422015545a59195db1dfcc79e837c81e54bdbf94 · 525,024 bytes

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