3,559,430 launches on record
Coverage from 2 Sep 2026
Archive read 02:56 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 18:53 UTC

FLOW

Flow

FiobQJe9nAnEGvWxVpY2nWovpGgQrxTFWi7fjep8FjLJ Solscan pump.fun
4.1%of supply taken by the creator in the first block
671outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
257launches carry this ticker, from 204 creator wallets
2other launches declared this same launch document, byte for byte
2other launches used this exact picture file
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 2 other launches, all of them this same creator's. 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.

noteThe creator sold while we were watching.
noteOnly 3.2 SOL of liquidity was in the pool just now.

At launch

Created2026-11-12 18:53 UTC
Creator7opb9tfmeDCLchVv91yLW7FD3cBhE3gS1bZVy3wCcpUC
Creator took4.1% of supply in the first block
Outside buyers671 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: 62 within the first 30s, 0 in the very same block the token was created in.
Graduated1.2 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 soldyes
Recorded from3mysEyrakZB3xyG7r6AMum… slot 468,632,567
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-12 18:53:03 UTC
Slot 468,632,567, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in62 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.
Highest price seen2026-11-12 19:08:13 UTC +15m 09s
3.495e-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.
Curve completed2026-11-12 20:02:08 UTC +1h 09m 04s
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 3 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 257 launches from 204 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.6% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 2 other launches, all of them this same creator's. Across the archive, 12% of the launches whose document we hold carry one only their own creator reused. See them →

Pool

Liquidity3.2 SOL
Read from chain2026-11-13 06:59 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameFlow
DescriptionFlow pays holders who stay: every 10 minutes, Flow transforms trading volume into USDC, rewarding the top 100 holders with a share of the rewards and your share grows from 1x to 25x the longer you hold.
Metadata heldsha256 8a73bf3af40d12ca1a662105db543af1d3ade9e4cbde6f2895c47b5bae76685c · 444 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 d1e4702cb05d29df87e8251ae5719ba220a342760d6715a2ee54b511ba60b53e · 76,932 bytes

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