3,493,064 launches on record
Coverage from 2 Sep 2026
Archive read 11 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-09-02 22:06 UTC

Gemini AI

Google Gemini

BoBiKJDJ96aqokJnk13BFZSoV83WF8p2Qp7hekh7pump Solscan pump.fun
79.3%of supply taken by the creator in the first block
0outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
186launches carry this ticker, from 185 creator wallets
1other launch declared this same launch document, byte for byte
55other launches used this exact picture file
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 55 other launches from 44 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, 56.2% 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 - 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.
noteThe creator sold while we were watching.
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.

At launch

Created2026-09-02 22:06 UTC
Creator3m8fFti9GfhNsPWc8yD8P4vHAduU1FZkdRe5JoHhGj9E
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: 66 within the first 30s, 0 in the very same block the token was created in.
Graduatedyes; we did not record when
Curve on chainComplete. We read the bonding curve account 63.0 days ago and it was finished. Checked 2026-09-09 23:50 UTC.
Creator soldyes
Recorded from4Vtgu6nrYN4zfDK3jjqpXv… slot 443,806,886
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-02 22:06:39 UTC
Slot 443,806,886, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in66 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-09-02 22:42:56 UTC +36m 17s
6.157e-6 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.
Curve completedRecorded as complete; we did not record when.
Confirmed against the venue's own completion state.

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 56 launches from 44 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 186 launches from 185 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 documentThe same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 33% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

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

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
NameGoogle Gemini
DescriptionThe Gemini app turns research into reality, bringing frontier AI experiences like Omni, Deep Think, Nano Banana, and more to hundreds of millions of people.
Metadata heldsha256 07912eb640ff4f44641d3a82e1f5804568370d0ba2fa5c19a1ca81679468561e · 428 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-09-23 00:38 UTC.
Picture heldsha256 5facd8dce3ce1bd6c68713395bacd4d6bceaa49af734f4ef29913c1921c62991 · 40,066 bytes

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