3,710,090 launches on record
Coverage from 2 Sep 2026
Archive read 06:29 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-09-16 13:26 UTC

Inucognito

BHWb6mXtMfTmnNyaFom6YSm4wgw61DF23PwD1kjXidgA 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 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. 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

9.5%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
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 creator has 1,843 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. They are listed under Seen before, further down this page.

1,844launches on record from this creator wallet, this one included, over 62 days
87on 8 Sep, its busiest day
853different tickers; the one it used most is BOB, 44 times
2 Sep: 363 Sep: 505 Sep: 96 Sep: 297 Sep: 298 Sep: 879 Sep: 4310 Sep: 7312 Sep: 3814 Sep: 2115 Sep: 4116 Sep: 3217 Sep: 5319 Sep: 3720 Sep: 4521 Sep: 4022 Sep: 4423 Sep: 5624 Sep: 4126 Sep: 6027 Sep: 3028 Sep: 3629 Sep: 3630 Sep: 161 Oct: 173 Oct: 664 Oct: 315 Oct: 376 Oct: 237 Oct: 638 Oct: 1010 Oct: 2011 Oct: 3512 Oct: 1413 Oct: 2714 Oct: 1415 Oct: 1317 Oct: 1218 Oct: 7019 Oct: 3320 Oct: 3121 Oct: 2925 Oct: 3026 Oct: 1427 Oct: 1228 Oct: 1029 Oct: 4130 Oct: 231 Oct: 71 Nov: 472 Nov: 363 Nov: 114 Nov: 235 Nov: 117 Nov: 188 Nov: 410 Nov: 3111 Nov: 612 Nov: 413 Nov: 214 Nov: 415 Nov: 4
2 SepThis creator wallet's launches per day (UTC)15 Nov
Its most recent other launches (UTC)TickerNameMint
15 Nov, 16:05Kidcoin Kidcoin██████████
15 Nov, 16:02Kidcoin Kidcoin██████████
15 Nov, 11:23Raped Raped██████████
15 Nov, 10:19Raped Raped██████████
14 Nov, 13:04Kidcoin Kidcoin██████████
14 Nov, 10:44HIGHER Higher██████████
See all of this creator's launches →

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-09-16 13:26 UTC
CreatorGeUnv1jmtviRbR7Gu1JnXSGkUMUgFVBHuEVQVpTaUX1W
Creator took9.5% 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.
Graduated6 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 from23P1ki34WXpDZST69nsg4P… slot 447,533,695
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.
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-09-16 13:26:54 UTC
Slot 447,533,695, which is the chain's own clock for this moment.
Highest price seen2026-09-16 13:26:54 UTC
0.000e+0 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.
Curve completed2026-09-16 13:33:08 UTC +6m 14s
Confirmed against the venue's own completion state.

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 pictureNo other launch we hold a picture for used this one.
This tickerOn 43 launches from 32 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.7% 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 2 creator wallets in all. Across the archive, 33.5% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator1,843 earlier launches, 12 confirmed complete on chain, 1 with findings on record. 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 835 other creator wallets, across 1,534 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.6% 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
NameInucognito
DescriptionCreated on https://rapidlaunch.io
Metadata heldsha256 fbeb622aadf1b7ade4b355ff1e589bf153548f8168397c392ecec1f24fa350be · 323 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-23 13:28 UTC.
Picture heldsha256 5195f1b06b02b019741db7c5a044b2d514a9f955f1fd8a329c3587fb09d9a1f8 · 12,240 bytes

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