3,485,057 launches on record
Coverage from 2 Sep 2026
Archive read 16:55 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-09 16:25 UTC

AVX

AVEXA

4E481AXn2wKxf61jwkXAQaLMhxFU5vWk3KZFyhPZpump Solscan pump.fun
3.7%of supply taken by the creator in the first block
9outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
6launches carry this ticker, from 6 creator wallets
Only 9 outside buyers bought its curveRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

findingOnly 9 outside buyers bought on the bonding curve before it graduated.

At launch

Created2026-11-09 16:25 UTC
Creator7UfU6tV3LTecAfNBis2NGgCtC7gJtZg565BQ2ypXQeAq
Creator took3.7% of supply in the first block
Outside buyers9 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: 7 within the first 30s, 3 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated13.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 from4NstTbCC6fjwywPp9vakS8… slot 467,383,839
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-09 16:25:29 UTC
Slot 467,383,839, which is the chain's own clock for this moment.
Creation block3 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in7 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-10 05:25:08 UTC +12h 59m 39s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-11-10 05:28:34 UTC +13h 03m 05s
4.923e-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.
This tickerOn 6 launches from 6 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.5% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

Liquidity113.6 SOL
Read from chain2026-11-11 19:01 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameAVEXA
Description🚀 AVEXA (AVX) – The Future of Digital Finance 💎 Advanced Crypto Payment Solutions 🤖 AI-Powered Technology ⚛️ Quantum-Ready Security Vision 🌐 Next-Generation Blockchain Innovation 🔗 Smart, Secure & Scalable Ecosystem AVEXA – Beyond Blockchain, Beyond Boundaries! Innovating Today. Empowering Tomorrow.
Metadata heldsha256 8d5021cff3617a3712498cbe3d0b66c2c474dca8c07b45ba4c17a652c17f2d43 · 632 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-11-10 22:07 UTC.
Picture heldsha256 359789cd75a6ab43d176ac10f36ca9be5aa643390cb2d6f820a64ba66e479f15 · 189,011 bytes

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