3,524,935 launches on record
Coverage from 2 Sep 2026
Archive read 13:18 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-12 07:37 UTC

ZEPHYRON

2Edt2MULcSzkmB2crp7doG8UHsqkakLLijeztiWapump Solscan pump.fun
69.1%of supply taken by the creator in the first block
32outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
16launches carry this ticker, from 3 creator wallets
15other launches used this exact picture file
The creator took 69% 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 15 other launches from 3 creator wallets in all, and this creator has 10 other launches 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, 56.3% of the launches whose picture we hold carry one a different creator also used. 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.

findingThe creator bought its own bonding curve - 54 SOL, from the same wallet that created the token.
findingThe creator took 69.1% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.
findingThat purchase is what completed the curve: the token left the curve on the creator's own money.
noteTook 4 bonding curves outright. 199 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 1.1 SOL of liquidity was in the pool just now.

At launch

Created2026-11-12 07:37 UTC
Creator279wv4A6kjW9SZdhdkmVPCiiw23By9P6WBqJ5oJ5SB3d
Creator took69.1% of supply in the first block
Outside buyers32 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: 16 within the first 30s, 2 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated1 min 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 from5eKsPapCr6oRVodqdoFET9… slot 468,444,154
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-12 07:37:48 UTC
Slot 468,444,154, which is the chain's own clock for this moment.
Creation block2 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in16 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-12 07:38:50 UTC +1m 02s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-11-12 07:38:50 UTC +1m 02s
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.

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 16 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 16 launches from 3 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.5% wear one that more than one creator wallet has launched. See this ticker's page →
This creator10 earlier launches, 1 confirmed complete on chain, 3 with findings on record. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, 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 3 creator wallets in all. Across the archive, 63.9% 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 54 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

Liquidity1.1 SOL
Read from chain2026-11-12 16:06 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameZEPHYRON
DescriptionThe pool locks at launch, the fee can only go down, and every buyer reads the rules before the first trade.
Metadata heldsha256 01cc25e23cd46c3e2160639d2ce42f33a66e3c81fae5734b147f95d3d7508e9b · 439 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 4cb8328f9776b12f2a3ce5dad2ff3b5d0a7cc2ea4ef049731f9e0b37147a040d · 329,978 bytes

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