3,627,313 launches on record
Coverage from 2 Sep 2026
Archive read 13:17 UTC today
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-14 00:58 UTC

Theo

Erzs5FwufhBSKeT61tspjD8KnMBQgzygQxkAZrKu2x6i 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

4.9%of supply taken by the creator in the first block
447outside 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 1 other launch, all of them this same creator's. 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, 12.8% of the launches whose picture we hold carry one only their own creator reused. 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 22.5 SOL of liquidity was in the pool just now.

At launch

Created2026-11-14 00:58 UTC
Creator3CRHTDgF3pv1zC8k8HUFZMioKKhVkT5z9DRrZ7svD9w6
Creator took4.9% of supply in the first block
Outside buyers447 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: 17 within the first 30s, 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.
Graduated6 min after launch
Curve on chainComplete. We read the bonding curve account 13.2 h ago and it was finished. Checked 2026-11-14 01:30 UTC.
Creator soldnot while we watched
Recorded from4EkW3pyAkbnEoqmLxy43am… slot 469,135,283
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-14 00:58:05 UTC
Slot 469,135,283, which is the chain's own clock for this moment.
Creation block5 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
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.
Curve completed2026-11-14 01:04:30 UTC +6m 26s
Confirmed against the venue's own completion state.
Highest price seen2026-11-14 01:04:30 UTC +6m 26s
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 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 238 launches from 196 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. Across the launches we watched at birth that stated a ticker, 89.6% wear one that more than one creator wallet has launched. 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 →

Pool

Liquidity22.5 SOL
Read from chain2026-11-14 14:45 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameTheo
Descriptiondeployed on https://track.tech/
Metadata heldsha256 5dbd9ed673f09c831d970794bc270ad251a68237fb1238194b0aea023e6b286d · 385 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 091c0b4330e42699e991485d68e79dcc580172ee95d1c9aff1efdcec813f2bd6 · 38,899 bytes

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