3,620,171 launches on record
Coverage from 2 Sep 2026
Archive read 06:28 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-10-04 22:57 UTC

๐Ÿš€

Rocket

EPP5fHh9M15MjyeEv7QJW2ikQHhsF9dzEkaaQy1FxBGB Solscan

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for five lists, or with Brand Protection at $79 a month for every list on every record. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

0.0%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
The curve completed 32s 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 15 other launches, all of them this same creator's, and this creator has 136 other launches on record. 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, 12.8% of the launches whose picture we hold carry one only their own creator reused. 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.

not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
findingIt left the curve 32s after launch.

At launch

Created2026-10-04 22:57 UTC
CreatorEZc5HSWaMU7cMEbCNsugJPB4Za3UgU2QemPsncm7NoUo
Creator took0.0% of supply in the first block
Outside buyersunknown 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.
Graduated1 min after launch
Curve on chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldnot recorded - this venue's trades do not name the wallet
Recorded from3UcyGtwowbmbqnioaR1w12โ€ฆ slot 453,397,131
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_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-10-04 22:57:12 UTC
Slot 453,397,131, which is the chain's own clock for this moment.
Curve completed2026-10-04 22:57:44 UTC +32s
Confirmed against the venue's own completion state.

Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.

Seen before

This pictureOn 16 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 834 launches from 139 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.6% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 13 other launches, all of them this same creator's. Across the archive, 12.1% of the launches whose document we hold carry one only their own creator reused. See them →
This creator136 earlier launches, 136 confirmed complete on chain. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 36 other creator wallets, across 34 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 so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.7% 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
NameRocket
Metadata heldsha256 728951aaa91aff553a728f96b9650246e09e778bc5c13a1dc31db3287337308d ยท 349 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 f2dd608d15ab83467a5ca0f28db47693b7d39aa383b3e4568548d0553b15c9ac ยท 11,465 bytes

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