3,649,476 launches on record
Coverage from 2 Sep 2026
Archive read 14 Nov 2026
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-25 23:55 UTC

Rawdog

rawdogmoon

3sVPfthvuhozzxhrcY7Q6iako4GWW3KQxgR4D3k6xjh9 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

6.7%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 picture is on 5 other launches from 5 creator wallets in all, and this creator has 948 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.5% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

949launches on record from this creator wallet, this one included, over 71 days
68on 24 Oct, its busiest day
669different tickers; the one it used most is ?, 19 times
2 Sep: 473 Sep: 144 Sep: 195 Sep: 16 Sep: 17 Sep: 28 Sep: 49 Sep: 1311 Sep: 1612 Sep: 1813 Sep: 914 Sep: 615 Sep: 416 Sep: 1917 Sep: 218 Sep: 219 Sep: 320 Sep: 222 Sep: 823 Sep: 1024 Sep: 225 Sep: 1726 Sep: 2627 Sep: 528 Sep: 130 Sep: 11 Oct: 42 Oct: 63 Oct: 34 Oct: 35 Oct: 96 Oct: 77 Oct: 28 Oct: 29 Oct: 210 Oct: 911 Oct: 212 Oct: 1813 Oct: 514 Oct: 715 Oct: 1416 Oct: 2617 Oct: 1418 Oct: 2219 Oct: 1520 Oct: 921 Oct: 2922 Oct: 823 Oct: 1524 Oct: 6825 Oct: 2726 Oct: 6027 Oct: 1428 Oct: 329 Oct: 1030 Oct: 531 Oct: 171 Nov: 62 Nov: 163 Nov: 84 Nov: 195 Nov: 466 Nov: 187 Nov: 88 Nov: 339 Nov: 1610 Nov: 2111 Nov: 412 Nov: 2013 Nov: 3614 Nov: 11
2 SepThis creator wallet's launches per day (UTC)14 Nov
Its most recent other launches (UTC)TickerNameMint
14 Nov, 19:08GREGORY Gregory McCarthy██████████
14 Nov, 18:10Cat Sword Cat██████████
14 Nov, 16:37kms kms██████████
14 Nov, 03:09theo its theo tho██████████
14 Nov, 02:46Python Python For Good██████████
14 Nov, 02:43inu 01101001 01101110 01110101██████████
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-25 23:55 UTC
Creator3z4vj1nAujLnciPgZaGz4VYecZa6gbYUg3Yr9MoyuiMG
Creator took6.7% 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.
Graduated14 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 fromB7dqSTrC9yrx3HrydftSg3… slot 450,506,522
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-25 23:55:21 UTC
Slot 450,506,522, which is the chain's own clock for this moment.
Highest price seen2026-09-25 23:55:21 UTC
2.796e-8 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-26 00:09:47 UTC +14m 26s
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 pictureOn 6 launches from 5 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 144 launches from 110 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 2 other launches, across 3 creator wallets in all. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator948 earlier launches, 27 confirmed complete on chain, 7 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 678 other creator wallets, across 1,185 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
Namerawdogmoon
Metadata heldsha256 6237afcd27432ce77c885e78630570dfe96e175f814d4d21c82c790e982748ca · 431 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-readThe address no longer served it when re-read 2026-10-02 23:56 UTC. The launch-time capture above is the surviving record.
Picture heldsha256 be1876253c4ab01ab7f123b5578d31e98b4902e3fc76d7a3804ef6c0e7535241 · 28,956 bytes

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