3,718,926 launches on record
Coverage from 2 Sep 2026
Archive read 13:20 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 10:13 UTC

i4x4

Ironman4x4

mGy48xEM6nZGKQK6amaiFfjXNp9GybUXCtd5LVNpump 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

0.9%of supply taken by the creator in the first block
25outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
The curve completed 16s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

Also recorded, and not part of the finding above: this picture is on 10 other launches, all of them this same creator's, and this creator has 19 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. 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.

findingIt left the curve 16s after launch.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.

At launch

Created2026-11-16 10:13 UTC
CreatorDJnD6YMAid5NQfzf3rzfmyAicxMXw4LxzKbcnPyoUTA6
Creator took0.9% of supply in the first block
Outside buyers25 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: 6 within the first 30s, 0 in the very same block the token was created in.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 5.2 h ago and it was finished. Checked 2026-11-16 10:32 UTC.
Creator soldyes
Recorded from3ZgQdVmJv9REfA2meZda1N… slot 470,093,867
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

Order of events

Created2026-11-16 10:13:29 UTC
Slot 470,093,867, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-11-16 10:13:46 UTC +16s
Confirmed against the venue's own completion state.
Thirty seconds in6 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 pictureOn 11 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 11 launches from 1 creator wallet, 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 documentThe same launch document, byte for byte, as 10 other launches, all of them this same creator's. Across the archive, 12.2% of the launches whose document we hold carry one only their own creator reused. See them →
This creator19 earlier launches. 3 reached the graduation threshold on our feed; we have read the curve account for 2, and 2 had not completed. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

Liquidity0.0 SOL
Read from chain2026-11-16 15:45 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameIronman4x4
Descriptionmeme coin
Metadata heldsha256 eeda1b9bc5c18602b4733e854525f85892dd5c9b205812df12262662b86792ff · 201 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 add8a09a6d057e62e560d53de59d8dd3cc9ddf4d165a8f7bbfe4fead24b239b9 · 14,226 bytes

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