2,376,848 launches on record
Coverage from 2 Sep 2026
Archive read 14:08 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

LMAO!

The curve completed 4s after 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 1 other launch from 2 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, 53.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.

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.

Daxa9wL9Tmr4ZCvbqXTo1dfUDE6rmZLr7boZZKtqpump Solscan pump.fun

Cite this record as: Chain of Title, LMAO! (Large Milkers All Over), mint Daxa9wL9Tmr4ZCvbqXTo1dfUDE6rmZLr7boZZKtqpump, observed at creation 2026-10-25 15:13 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Daxa9wL9Tmr4ZCvbqXTo1dfUDE6rmZLr7boZZKtqpump

rebuilt We did not watch this launch. Its record was reconstructed from the bonding curve's complete transaction history, so the figures below are the same on-chain events, read later. What it cannot tell you is what the token claimed to be at launch: the name, image and links live off-chain and can be changed since.

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.

findingIt left the curve 4s after launch.

At launch

Created2026-10-25 15:13 UTC
Creator6nYSamo91eZ5wNeMx7NDgoYeGyYQ2fBpW8PBsLDRb68m
Creator took0.2% of supply in the first block
Outside buyers17 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.
Graduated0 min after launch
Curve on chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldno
Recorded from3k8ygH627Y8RSpExnhfNns… slot 461,303,876
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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.

Order of events

Created2026-10-25 15:13:07 UTC
Slot 461,303,876, which is the chain's own clock for this moment.
Creation block17 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-10-25 15:13:11 UTC +4s
Confirmed against the venue's own completion state.
Thirty seconds in17 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. Across the archive, 53.2% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 79 launches from 59 creator wallets. 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, 88.2% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 3 other launches, across 3 creator wallets in all. Across the archive, 30.3% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

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
NameLarge Milkers All Over
DescriptionA wild meme-fueled frenzy where big milkers rule the internet and the meme madness never stops!
Metadata heldsha256 67bf1fa1ffdbc433824ea9612dbbb64d7c5c2ede9764005677d0e689edbeb943 · 416 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 838a1770e01890d3e071c65b6e5f25b920ad67ad0a49f00ac73009418b59243f · 438,442 bytes

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