653,438 launches on record
Coverage from 2 Sep 2026
Archive read 07:17 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

WEIRDCAT

The curve completed 53s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.

DZerK3hU9DD1wpnrDqBebSyZ8EhMczG77SphJY3ppump Solscan pump.fun
findingIt left the curve 53s after launch.
noteOnly 0.6 SOL of liquidity was in the pool just now.

At launch

Created2026-09-23 02:32 UTC
CreatorGM7A8dWMotCd5kGMENfe9CF5ZpDdVmn7VqoD4Mc8tBkj
Creator took0.2% of supply in the first block
Outside buyers20 distinct wallets, not counting the creator, bought on the bonding curve: 3 within the first 30s, 0 bundled into the creation block.
Graduated1 min after launch
Curve, read on chainComplete. We read the bonding curve account 7.3 h ago and it was finished. Checked 2026-09-23 02:46 UTC.
Creator soldnot while we watched
Recorded from27zEPhYXEHAcLQoU1i5TCK… slot 449,568,342
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-23 02:32:15 UTC
Slot 449,568,342, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in3 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-09-23 02:33:08 UTC +53s
Confirmed against the venue's own completion state.
Highest price seen2026-09-23 02:33:08 UTC +53s
1.240e-7 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.

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 167 launches from 94 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 223 launches from 105 creator wallets, including this one. See them →
This documentByte-identical to 33 other launches' metadata document. See them →
This creator6 earlier launches, 0 confirmed graduated on chain. See the creator's launches →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 7 other creator wallets, across 4 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets →

Pool

Liquidity0.6 SOL
Read from chain2026-09-23 10:02 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameWeird Cat
Metadata heldsha256 2dbd6fed86b47c116f0303875039c6050f00e56c9c25b6a163c624f9f188c131 · 195 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 04aff93eeffbebb8142bfc4e49dc827b57d19fa32ded655d55e6105e12a041f7 · 100,399 bytes

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