629,737 launches on record
Coverage from 2 Sep 2026
Archive read 16:23 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

TRUMPGRILL

The curve completed in the same batch of events as the launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

Cwt1EDyRKVnrzGky9rpmn7Mgq8ywgzGfzZyuv2EMpump Solscan pump.fun
findingOnly 8 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.

At launch

Created2026-09-21 10:50 UTC
CreatorGT71QHrh99v4QnVRNNSdUKmCo622VLfoWQUx4CuN2ozc
Creator took0.0% of supply in the first block
Outside buyers8 distinct wallets, not counting the creator, bought on the bonding curve: 8 within the first 30s, 8 bundled into the creation block.
Graduated0 min after launch
Curve, read on chainComplete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-21 11:11 UTC.
Creator soldnot while we watched
Recorded from54a69Q6R6vgatXYsGFcjvg… slot 449,033,444
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-21 10:50:57 UTC
Slot 449,033,444, which is the chain's own clock for this moment.
Creation block8 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-09-21 10:50:57 UTC +0s
Confirmed against the venue's own completion state.
Highest price seen2026-09-21 10:50:57 UTC +0s
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.
Thirty seconds in8 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 pictureNo other launch we hold a picture for used this one.

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
Nametrumpgrill
DescriptionTRUMPGRILL
Metadata heldsha256 4468c63de1910e4742ccf3eef63bc62fc85b3eae8b773e23783fcd96463c9bbc · 332 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.
Document re-readByte-identical to the launch-time capture when re-read 2026-09-22 11:37 UTC.
Picture heldsha256 723bfe82c85a99fc12f6710bb5942ceeb7d409fe9ba9b1f48dde5324eaeeb181 · 276,197 bytes

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