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

Koala

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 creator has 564 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. They are listed under Seen before, further down this page.

A record of what this launch was at birth, read from the Solana chain. We did not record its creation transaction, so these figures rest on our observation at the time rather than on a citation you can follow. Not a prediction and not advice.

sPwh55WJoHpTmHTeyNYNKxJizovzrNwKCsqwMH2pump Solscan pump.fun

At launch

Created2026-09-02 16:03 UTC
Creator6FGsiDL3GAFQ3duWJMakqcjKqC2n69XooYjGU2YpCR5M
Creator took3.4% of supply in the first block
Outside buyersunknown 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: 5 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.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldnot while we watched
Recorded fromNot recorded. This launch predates our keeping the creation transaction (2026-09-09), and its trade rows had been pruned by retention before the backfill could recover the signature from them. The figures above stand on our own observation alone, which is weaker than a citation, and we would rather say so than leave the gap unmarked.
Not recordedcurve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement. snap30_buyers - no thirty-second snapshot was taken, and that snapshot is meaningful only for an observed launch.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

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-09-02 16:03:01 UTC
Creation block5 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Highest price seen2026-09-02 16:03:01 UTC
3.257e-8 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.

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 pictureNo other launch we hold a picture for used this one.
This tickerOn 41 launches from 33 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 →
This creator564 earlier launches, 1 confirmed complete on chain, 1 with findings on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 14 other creator wallets, across 31 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 so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. See the linked wallets →

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
NameThe G20 Animal
DescriptionG20 Koalas — the unofficial animal of the summit In 2014 at the Brisbane G20, world leaders didn’t remember the communiqué. They remembered the koala. Obama laughed. Putin smiled. Modi posed. Merkel reached in. One 2-year-old named Jimbelung stole the whole meeting.
Metadata heldsha256 bcf024a366df6032dc823fe32ed3362f1d24978d45e7a2857dee688d6e4c00dd
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 060d09080e89c05a7cdf83f1966b94100e75845ae0ea8d807999e29a83e8a959 · 1,867,135 bytes

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