3,740,817 launches on record
Coverage from 2 Sep 2026
Archive read 20:11 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-16 17:50 UTC

SENT

Sent

3EDLvS4PMWXmN5oj7aGWwR16yC3zgZSdWL2BeVK8sent 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 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. 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

3.5%of supply taken by the creator in the first block
731outside 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 creator has 2 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.

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 11.8 SOL of liquidity was in the pool just now.

At launch

Created2026-11-16 17:50 UTC
CreatorcashcTxrzesgpdPhY4kzf6qvAWkokjVUExM9tZJGPC9
Creator took3.5% of supply in the first block
Outside buyers731 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: 88 within the first 30s, 0 in the very same block the token was created in.
Graduated3.0 h after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded from2geJ1mSiEQQJYB6xgWLzJM… slot 470,221,795
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-16 17:50:58 UTC
Slot 470,221,795, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in88 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-16 20:53:00 UTC +3h 02m 02s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-11-16 20:53:05 UTC +3h 02m 07s
1.082e-6 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 pictureNo other launch we hold a picture for used this one.
This tickerOn 109 launches from 103 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.7% wear one that more than one creator wallet has launched. See this ticker's page →
This creator2 earlier launches, 1 confirmed complete on chain. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, across 3 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 so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.6% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity11.8 SOL
Read from chain2026-11-16 23:49 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameSent
DescriptionDeployed using https://j7tracker.io
Metadata heldsha256 34b6cd92ed5b02c8d39f7c080ce4ca74c9fc1d4d3c79284ce29073d337c8172f · 225 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 3298bee2387bea14cd222c966d40d55fd51fdd3b0731ca644d6bcda12bbc0e91 · 4,816 bytes

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