1,281,375 launches on record
Coverage from 2 Sep 2026
Archive read 12:03 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

MSAI

The creator took 79% of supply at 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 1 other launch from 2 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, 44.5% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

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.

BXcVVYNa3eojfTuJfmqEtzxHmqLJD5obUDbZiYrGpump Solscan pump.fun

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.

findingThe creator bought its own bonding curve - 85 SOL, from the same wallet that created the token.
findingThe creator took 79.3% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.
noteTook 1 bonding curve outright. 85 SOL spent on curves. We hold no market trades for it in either direction, so what it did with the tokens afterwards is not on our record.
noteOnly 0.4 SOL of liquidity was in the pool just now.

At launch

Created2026-10-03 08:44 UTC
CreatorFkf4Hh4TAxeJJNGeKGp2gV5Pw8m1Ezh7qEBHAseEm2pP
Creator took79.3% of supply in the first block
Outside buyers0 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: 0 within the first 30s, 0 in the very same block the token was created in.
Graduatedyes; we did not record when
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 from5FK6AGHBPGdApMFMWYSiyC… slot 452,883,108
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-10-03 08:44:16 UTC
Slot 452,883,108, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Highest price seen2026-10-03 08:44:16 UTC
4.109e-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.
Thirty seconds inNo 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.
Curve completedRecorded as complete; we did not record when.
Confirmed: a PumpSwap pool was found for it.

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 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 5 launches from 5 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. See this ticker's page →
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. 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 the creator's own wallet. The wallet and the transaction →

That is the same transaction the token was created in: the launch and the purchase of its float are one signature.

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

Liquidity0.4 SOL
Read from chain2026-10-03 15:04 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameMicrosoft AI
Metadata heldsha256 b57cac1c7d964b622a22a0b809b26610304ffefe576b962b73f992bf500d6396 · 359 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 3588645bf9040a5c50084fb2da272ebf8f35e7d70bf4cb1a2e63232e8eeaf964 · 87,365 bytes

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