1,199,589 launches on record
Coverage from 2 Sep 2026
Archive read 00:03 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

$CR7

No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.

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.

7oEoFMgmkWtAVzpE9aLTzaTSVdbqxdKLRXZf138vpump Solscan pump.fun

At launch

Created2026-10-01 18:26 UTC
CreatorCxGNZEcb49twMdANmXf3Yu1zf4CNrbaT8BWNJzqnxyq9
Creator took0.3% of supply in the first block
Outside buyers10 distinct wallets, not counting the creator, bought on the bonding curve: 1 within the first 30s, 0 bundled into the creation block.
Graduated2 min after launch
Curve, read on chainComplete. We read the bonding curve account 7.4 h ago and it was finished. Checked 2026-10-01 20:01 UTC.
Creator soldnot while we watched
Recorded from5gL44KYAsiLnL7mTrAxPo5… slot 452,367,610
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-10-01 18:26:07 UTC
Slot 452,367,610, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in1 distinct buyer, 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-01 18:28:10 UTC +2m 03s
Confirmed against the venue's own completion state.
Highest price seen2026-10-01 18:28:10 UTC +2m 03s
1.089e-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 4 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 8 launches from 6 creator wallets, including this one. See them →
This documentByte-identical to 2 other launches' metadata document. See them →
Birth artifactsLaunches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets →

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
NameCristiano Ronaldo
DescriptionBorn to win. Built to dominate.
Metadata heldsha256 7a95f1ad28d0dff39f4413dd9bcd8222914272f4cede81202c44990a510a387d · 230 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 a436ba275635c9b35cd03941babd44099387bfe1afe6b20a286bfeaf74de2af7 · 279,955 bytes

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