628,663 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

ARMCO

Only 3 outside buyers bought its curveRead 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.

9wUTaA8feYRmpVRCGYKM8LZbbf5oA78R5t369PHwpump Solscan pump.fun
findingOnly 3 outside buyers bought on the bonding curve before it graduated.

At launch

Created2026-09-22 08:04 UTC
CreatorAvQnvd7YCMMGge74VxnZEbTsj8CJgmMGTkwvn1n9dvGZ
Creator took0.2% of supply in the first block
Outside buyers3 distinct wallets, not counting the creator, bought on the bonding curve: 2 within the first 30s, 1 bundled into the creation block.
Graduated1.2 h after launch
Curve, read on chainComplete. We read the bonding curve account 6.7 h ago and it was finished. Checked 2026-09-22 11:04 UTC.
Creator soldnot while we watched
Recorded from3P5siiB4WeNEGjSTn9YnUG… slot 449,319,465
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-22 08:04:56 UTC
Slot 449,319,465, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in2 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-09-22 09:19:27 UTC +1h 14m 31s
Confirmed against the venue's own completion state.
Highest price seen2026-09-22 09:19:27 UTC +1h 14m 31s
1.286e-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 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
NameARMCO
DescriptionOil and gas blockchain contracts.
Metadata heldsha256 59b574c63a1232251b5880b8c8713b49fa39e2e67cf8d67cc3c1b5ef297608d1 · 290 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 edce1c41f6cf21f6c339d83a8995f644f22b27239ae850586ed4b365d7244fcd · 250,519 bytes

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