1,237,522 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

PERRO

The curve completed in the same batch of events as the launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

5tckuF9AczEH59JtQA1DX72ATzSR6k7k8Nt2jhHtpump Solscan pump.fun
findingIt left the curve 0s after launch.

At launch

Created2026-10-02 15:15 UTC
CreatorAxi22vQrda6GNe2BAyUn1wVvHgaq2WMZz8x8FQNp8K5p
Creator took0.0% of supply in the first block
Outside buyers10 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 10 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 4.6 h ago and it was finished. Checked 2026-10-02 15:31 UTC.
Creator soldnot while we watched
Recorded from4mjM7fLDYnZz7w2RCksdPg… slot 452,647,852
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-02 15:15:48 UTC
Slot 452,647,852, which is the chain's own clock for this moment.
Creation block10 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-10-02 15:15:48 UTC +0s
Confirmed against the venue's own completion state.
Highest price seen2026-10-02 15:15:48 UTC +0s
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 in10 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.

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 18 launches from 18 creator wallets, including this one. See them →
This documentByte-identical to 1 other launch's metadata document. See them →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. 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
NamePERRO
DescriptionToo small for the timeline. Too dripped out for the kennel. One pup. One impossible hat. Infinite PERRO.
Metadata heldsha256 2bc363da87f61f1ae9367b9a34e2d52e7b2bf07be46aedd7f73b5fa6d0182091 · 410 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 30d72f4e00f24c21c945f988dfedb916dc7b21a4184affd0d0b36b0ab84b05c8 · 139,618 bytes

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