3,742,437 launches on record
Coverage from 2 Sep 2026
Archive read 16 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-10-02 16:30 UTC

MEE

ITSMEE

GkhVgpiYysDHPvZReEE7uLCVSZLPm7KZP4GAcCDFpump 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. 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

0.3%of supply taken by the creator in the first block
21outside wallets bought on the bonding curve
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 1 other launch, all of them this same creator's, and this creator has 1 other launch 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, 12.8% of the launches whose picture we hold carry one only their own creator reused. 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.

noteOnly 0.0 SOL of liquidity was in the pool just now.

At launch

Created2026-10-02 16:30 UTC
Creator94XsRe3BjvfJ74EzqRWMRyx9LGKz1KEKrvU2jDDdGcce
Creator took0.3% of supply in the first block
Outside buyers21 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: 10 within the first 30s, 0 in the very same block the token was created in.
Graduated1.0 h after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded from5oNqjTqQ1Nx7sBzbE5vZP5… slot 452,664,693
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-02 16:30:53 UTC
Slot 452,664,693, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in10 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-10-02 17:31:42 UTC +1h 00m 50s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-02 17:31:42 UTC +1h 00m 50s
0.000e+0 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.

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 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 19 launches from 15 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.7% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 1 other launch, all of them this same creator's. Across the archive, 12.2% of the launches whose document we hold carry one only their own creator reused. See them →
This creator1 earlier launch, 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 →

Pool

Liquidity0.0 SOL
Read from chain2026-11-17 03:54 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameITSMEE
DescriptionItsMee Memecoin - No Utility - Made by BTC OG
Metadata heldsha256 6d841f7e2faa4ff09ec011382a5421d118339dd0c012b6db4c64b3f13d38da59 · 270 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-10-24 01:17 UTC.
Picture heldsha256 9ad0b5509fa75b336bf8d7743b477d966fe2b2f42ac9a734f6ca7d83451486e3 · 87,137 bytes

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