2,325,483 launches on record
Coverage from 2 Sep 2026
Archive read 03:58 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

SMUGLY

The curve completed 35s 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 6 other launches, and this creator has 5 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. 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.

Ae1xpHh1gEmwBRHw9vKiAEKoAvNs5HFD3bgrT5Npump Solscan pump.fun

Cite this record as: Chain of Title, SMUGLY, mint Ae1xpHh1gEmwBRHw9vKiAEKoAvNs5HFD3bgrT5Npump, observed at creation 2026-10-24 02:38 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Ae1xpHh1gEmwBRHw9vKiAEKoAvNs5HFD3bgrT5Npump

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 35s after launch.
noteTook 1 bonding curve outright. 150 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-10-24 02:38 UTC
CreatorEZkoC1KqQNnJbaPQDDkCZc9BvT6QbfWm2L4BCutSwXKx
Creator took9.7% of supply in the first block
Outside buyers19 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: 16 within the first 30s, 1 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.
Graduated1 min after launch
Curve on chainComplete. We read the bonding curve account 3.9 h ago and it was finished. Checked 2026-10-24 03:02 UTC.
Creator soldnot while we watched
Recorded from4GhPJn1UQoNE8ML1AsNKis… slot 460,683,556
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

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.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-24 02:38:41 UTC
Slot 460,683,556, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in16 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.
Curve completed2026-10-24 02:39:16 UTC +35s
Confirmed against the venue's own completion state.
Highest price seen2026-10-24 02:39:16 UTC +35s
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.

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 creator5 earlier launches. Across the archive, 70.1% of launches come from a creator with more than one launch on record. See the creator's launches →

Who took the curve

One transaction bought 67 SOL of this curve, in the same batch of events as the launch, from a wallet other than the creator's. The wallet and the transaction →

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
NameSMUGLY
DescriptionBorn in dirt. Raised in gold. The only coin that looks at you like you’re the problem. Stay Smugly.
Metadata heldsha256 35bf99b17f4a10ff577e2dcd6acc11e66011bc1b455798067365ba78db63a271 · 342 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 b32f8adba4dbfc5cc7ee14f680b5fd4d6ef4f2d9129988c16e279b8abe3b100c · 3,051,933 bytes

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