3,966,001 launches on record
Coverage from 2 Sep 2026
Archive read 04:02 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-11-21 03:26 UTC

GRINLO

Grinlo

CjUYtohUCUBJDAzbUSGWHGMkqyHcBqtbALDtceh7pump Solscan pump.fun

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.

Its own first blocks

0.4%of supply taken by the creator in the first block
1outside wallet bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed in the same batch of events as the launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

Also recorded, and not part of the finding above: this picture is on 5 other launches from 5 creator wallets in all. 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.

rebuilt We did not watch this launch. Its record was reconstructed from the bonding curve's complete transaction history, so the figures below are the same on-chain events, read later. What it cannot tell you is what the token claimed to be at launch: the name, image and links live off-chain and can be changed since.

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.

findingOnly 1 outside buyer bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
findingSold into the market, bought back little. Took 48 bonding curves outright for 4,002 SOL and sold 385 SOL into buyers on the open market, buying back nothing.

At launch

Created2026-11-21 03:26 UTC
CreatorF9Mb3QAcJVgKXYnjHBkPEneT63XXyKdjYThMaujT66Mm
Creator took0.4% of supply in the first block
Outside buyers1 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.
Graduated0 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 soldno
Recorded fromkeJeFmyKjybcenWZEJJ2k1… slot 471,987,685
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_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-11-21 03:26:06 UTC
Slot 471,987,685, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-11-21 03:26:06 UTC +0s
Confirmed against the venue's own completion state.
Thirty seconds in1 distinct buyer, within the first thirty seconds.
A snapshot taken off a tick at the thirty-second mark, so it carries no moment of its own; it is placed here because that is where it happened.

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.9% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 6 launches from 5 creator wallets. 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 4 other launches, across 4 creator wallets in all. Across the archive, 33.6% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 4 other creator wallets, across 3 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 →

Who took the curve

One transaction bought 85 SOL of this curve, in the same batch of events as the launch, from a wallet other than the creator's. The wallet and the transaction →

Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.

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
NameGrinlo
DescriptionGrinlo The purple bald crawler who never stands and never stops smiling. Born from pure degen energy in the trenches. He doesn’t walk. He crawls. Once you see the grin… it’s already too late.
Metadata heldsha256 b261a157e5f49ad98390702fb56c432a3f6bc6686e4d00d6c566121191681bbd · 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.
Picture heldsha256 c18a4371cd3ba11fe09d6a0b5d55a0f42cfc42e201fe42b6a2ebaa12650cb80f · 954,129 bytes

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