3,937,497 launches on record
Coverage from 2 Sep 2026
Archive read 14:13 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-23 21:33 UTC

가토

Gato

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

531launches on record from this creator wallet, this one included, over 64 days
36on 23 Sep, its busiest day
391different tickers; the one it used most is MEMESTOCK, 8 times
2 Sep: 33 Sep: 54 Sep: 16 Sep: 17 Sep: 78 Sep: 59 Sep: 1710 Sep: 611 Sep: 414 Sep: 115 Sep: 118 Sep: 120 Sep: 521 Sep: 222 Sep: 1823 Sep: 3624 Sep: 625 Sep: 1726 Sep: 827 Sep: 328 Sep: 430 Sep: 71 Oct: 112 Oct: 193 Oct: 24 Oct: 315 Oct: 126 Oct: 107 Oct: 128 Oct: 119 Oct: 211 Oct: 912 Oct: 2013 Oct: 414 Oct: 115 Oct: 1216 Oct: 1017 Oct: 1118 Oct: 819 Oct: 220 Oct: 322 Oct: 923 Oct: 2525 Oct: 526 Oct: 2327 Oct: 1328 Oct: 1929 Oct: 1630 Oct: 151 Nov: 12 Nov: 103 Nov: 64 Nov: 145 Nov: 36 Nov: 28 Nov: 19 Nov: 113 Nov: 414 Nov: 115 Nov: 216 Nov: 417 Nov: 219 Nov: 320 Nov: 4
2 SepThis creator wallet's launches per day (UTC)20 Nov
Its most recent other launches (UTC)TickerNameMint
20 Nov, 19:23PI Pop Inu██████████
20 Nov, 19:19Titan TitanCoin██████████
20 Nov, 10:48RUDY Rudolph██████████
20 Nov, 10:42RUDY Rudolph██████████
19 Nov, 23:48SI Spy Inu██████████
19 Nov, 23:11Termix Termix██████████
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-23 21:33 UTC
Creator2GBkFfJwjMkFTNvng4eUKgGi2reR7MxcPVWye8ai8pvU
Creator took9.2% 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 from5rUC7KND6Df623PBcv7oCT… slot 449,826,372
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-23 21:33:23 UTC
Slot 449,826,372, which is the chain's own clock for this moment.
Highest price seen2026-09-23 21:33:23 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-23 21:38:57 UTC +5m 34s
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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.9% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 3 launches from 3 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.9% 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.5% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator528 earlier launches, 12 confirmed complete on chain, 2 with findings on record. Across the archive, 70.6% 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 356 other creator wallets, across 546 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.4% 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
NameGato
DescriptionCreated on https://rapidlaunch.io
Metadata heldsha256 ba79f7452f2e877783e5c287158c7d1017abe991bcbb31f75f3b56f2d77ddf2e · 261 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-30 21:34 UTC.
Picture heldsha256 7f8b8a2aa47acf46b489333fa2e5868c6ebc524a9f59dcacc52a55c86f957cc3 · 10,664 bytes

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