3,899,874 launches on record
Coverage from 2 Sep 2026
Archive read 19 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-11-19 16:51 UTC

CATMARIO

NEKOMARIO

HUwPBFx3nzvxHXK3Ufsj2iYgVuoR8eDUVers7yG5pump 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

11.3%of supply taken by the creator in the first block
100outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
Checked at birth, no markers foundWe reconstructed this launch from its complete on-chain history and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 11.3%, 100 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.

Also recorded, and not part of the finding above: this picture is on 25 other launches from 22 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.8% 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.

At launch

Created2026-11-19 16:51 UTC
Creator7TbnqozWG7gvmMu9XG1GYoFwd6UnLm44nB2eG8HsiPAA
Creator took11.3% of supply in the first block
Outside buyers100 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.
Graduated3 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 from3HRQEWTQi3WGKwfWMYgf7x… slot 471,409,192
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-19 16:51:36 UTC
Slot 471,409,192, which is the chain's own clock for this moment.
Creation block11 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in40 distinct buyers, 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.
Curve completed2026-11-19 16:54:28 UTC +2m 52s
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 25 launches from 22 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.8% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 98 launches from 80 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.8% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 3 other launches, across 4 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 →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 1 other creator wallet, across 2 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 of 2 creator wallets in all. Across the archive, 63.5% 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
NameNEKOMARIO
DescriptionDeployed using https://j7tracker.io
Metadata heldsha256 9e5d5648c32aec124eac194e9c6959b7147a17ee2cfa331de4b00b56c4bab06c · 308 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 de7cdb0ae74e9d07c6ba5edbcb103689766fb09e65171442c1981d35b9701ca6 · 157,054 bytes

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