Launch record · observed at creation 2026-09-22 17:24 UTC

R

ape

CshRpBHPqD1C9cbbnJ9Ki7PmQr7hiDLJ9A7ejg5AAXsy Copy 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

Also recorded, and not part of the finding above: this creator has 38 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.

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

Created	2026-09-22 17:24 UTC
Creator	2LNs9dtv19wrNx6WnqJPJfAinz9A3KVh2xuMZHiSxoHt
Creator took	0.0% of supply in the first block
Outside buyers	unknown 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.
Graduated	2 min after launch
Curve on chain	Not 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 sold	not recorded - this venue's trades do not name the wallet
Recorded from	5d6QEeWfPnFGQZ4P8Y4ePH… slot 449,445,361 The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recorded	curve_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

Created	2026-09-22 17:24:52 UTC Slot 449,445,361, which is the chain's own clock for this moment.
Curve completed	2026-09-22 17:26:33 UTC +1m 41s 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 picture	No other launch we hold a picture for used this one.
This ticker	On 160 launches from 95 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 creator	38 earlier launches, none of which reached a graduation threshold while we watched. 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 wallets	Launches by this creator were made with files byte-identical to those of 10 other creator wallets, across 21 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

Name	ape
Description	ape was launched on StonkFun.
Metadata held	sha256 4e73a4ed588f81ccca3359223169a7d0634575aac230ab7a232f839af8c33b7a · 441 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-read	Byte-identical to the launch-time capture when re-read 2026-09-29 17:26 UTC.
Picture held	sha256 263327ad24517b4c7ac5396989d166c84dfb61d2cecfee19123552a02243393d · 76,123 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-09-22 17:24 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.