3,490,400 launches on record
Coverage from 2 Sep 2026
Archive read 16:55 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-23 17:36 UTC

pill

D9jB8FdbuPQmoUw4rH62qT2cAQFLtvsATVRvVN7VGyhU Solscan
0.0%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
1,646launches carry this ticker, from 1,191 creator wallets
1other launch declared this same launch document, byte for byte
1other launch used this exact picture file
No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 1 other launch, all of them this same creator's, and this creator has 7 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.

At launch

Created2026-10-23 17:36 UTC
CreatorBDtKeKASRanp2iTYsee1HowWTwmgLvtETjY2QrQcoKu4
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.
Graduated7 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 from48Pr7uYD2xPYLdmtJzvxTd… slot 460,530,347
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-23 17:36:27 UTC
Slot 460,530,347, which is the chain's own clock for this moment.
Curve completed2026-10-23 17:43:35 UTC +7m 08s
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 2 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 1,646 launches from 1,191 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 1 other launch, all of them this same creator's. Across the archive, 12% of the launches whose document we hold carry one only their own creator reused. See them →
This creator7 earlier launches, 7 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 →

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
Namepill
Metadata heldsha256 67549237b80cbfa256c42195c18e441c90882637c3cc408068c6c4d9d1cc4521 · 406 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 ba57df2dabe644c01c6abd044e8c905510cbd95c555c2d6d710232226e0fd117 · 1,830 bytes

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