3,527,037 launches on record
Coverage from 2 Sep 2026
Archive read 13:18 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-09 14:05 UTC

牛逼

ETwYRQhn1ASUNJ8xYEu4pFeKPcMij5NVw5y2xZRfoCtx Solscan
19.9%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
203launches carry this ticker, from 152 creator wallets
12other launches declared this same launch document, byte for byte
51other launches used this exact picture file
The curve completed in the same batch of events as the 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 51 other launches from 17 creator wallets in all, and this creator has 9 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, 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.

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 0s after launch.

At launch

Created2026-11-09 14:05 UTC
Creator9yn3iG3ULBiRqHk6DsY6XspotH7k1LCqikbwAoB5hSRs
Creator took19.9% 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.
Graduatedin the same batch of events as the 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 from4DiyB19yBg8ohXTvNXfbPs… slot 467,344,794
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-11-09 14:05:45 UTC
Slot 467,344,794, which is the chain's own clock for this moment.
Curve completed2026-11-09 14:05:45 UTC
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 52 launches from 17 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 203 launches from 152 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 12 other launches, across 5 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 →
This creator9 earlier launches, 9 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 8 other creator wallets, across 4 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.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
Name牛逼
Metadata heldsha256 11be0f9bb40dc6b41a4c77c6635d54b66946132983e21c9f07cf3e020ab0a25a · 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 d588d4999bf39ff6ff0ff6ea1d57e24a66d2138595baf1c2ecf589bad34caf00 · 1,289 bytes

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