3,608,752 launches on record
Coverage from 2 Sep 2026
Archive read 13 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-11-13 18:49 UTC

ALETH

Aleth Intel

4hdUC8v8KqmNgCBe1jkUoGHLqHtWZfBzaH9BSC3Lpump Solscan pump.fun

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for five lists, or with Brand Protection at $79 a month for every list on every record. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

2.2%of supply taken by the creator in the first block
389outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.

Also recorded, and not part of the finding above: this picture is on 6 other launches from 6 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.5% 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.

noteOnly 3.2 SOL of liquidity was in the pool just now.

At launch

Created2026-11-13 18:49 UTC
Creator6iydpTt4jLXCHkTTAt2dSUCKSKEZtouf7Zs76bVHFoPi
Creator took2.2% of supply in the first block
Outside buyers389 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: 113 within the first 30s, 12 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.
Graduated3 min after launch
Curve on chainComplete. We read the bonding curve account 10.5 h ago and it was finished. Checked 2026-11-13 19:00 UTC.
Creator soldnot while we watched
Recorded fromg69PegiuHWjLio22nh5Njb… slot 469,032,482
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-13 18:49:13 UTC
Slot 469,032,482, which is the chain's own clock for this moment.
Creation block12 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in113 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-11-13 18:51:46 UTC +2m 33s
Confirmed against the venue's own completion state.
Highest price seen2026-11-13 18:51:46 UTC +2m 33s
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 pictureOn 7 launches from 6 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 24 launches from 21 creator wallets, including this one. See this ticker's page →
This documentThe same launch document, byte for byte, as 1 other launch, all of them this same creator's. Across the archive, 12.1% of the launches whose document we hold carry one only their own creator reused. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 5 other creator wallets, across 2 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 of 9 creator wallets in all. Across the archive, 63.7% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity3.2 SOL
Read from chain2026-11-14 05:28 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameAleth Intel
Metadata heldsha256 b576b2cb0b5aad0959f7a65d0a9fafe47651c7ae830713bfb2e6f1c4391fffa7 · 269 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 4af8be5085b1e04d93755fd264102d10f727440cd04d0d6b14e8b1468d1b4514 · 38,798 bytes

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