3,203,072 launches on record
Coverage from 2 Sep 2026
Archive read 5 Nov 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

AAAAAAAAAAAAA

Checked at birth, no markers found; pool below threshold when last readWe reconstructed this launch from its complete on-chain history and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.

Also recorded, and not part of the finding above: this picture is on 24 other launches from 4 creator wallets in all. 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, 55.3% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

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.

Bi59TGKZgLa7zVRz1BX3yPg6Cj8wWfZwfNc5FaCApump Solscan pump.fun

Cite this record as: Chain of Title, AAAAAAAAAAAAA (aaaaaaaaaaaaaaaa), mint Bi59TGKZgLa7zVRz1BX3yPg6Cj8wWfZwfNc5FaCApump, observed at creation 2026-11-05 21:18 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Bi59TGKZgLa7zVRz1BX3yPg6Cj8wWfZwfNc5FaCApump

rebuilt We did not watch this launch. Its record was reconstructed from the bonding curve's complete transaction history, so the figures below are the same on-chain events, read later. What it cannot tell you is what the token claimed to be at launch: the name, image and links live off-chain and can be changed since.

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.

noteOnly 0.0 SOL of liquidity was in the pool just now.

At launch

Created2026-11-05 21:18 UTC
Creator7z3ppX88WqXX5GxtPdB6ffRdHkr9S8coVLACc6NRwBCJ
Creator took12.8% of supply in the first block
Outside buyers210 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.
Graduated1 min 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 soldno
Recorded from52KY4Ra43dumMxEgznj3iU… slot 465,854,248
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-05 21:18:52 UTC
Slot 465,854,248, which is the chain's own clock for this moment.
Creation block2 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Highest price seen2026-11-05 21:18:52 UTC
0.000e+0 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 in141 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-05 21:20:16 UTC +1m 24s
Confirmed: a PumpSwap pool was found for it.

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 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 55.3% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 14 launches from 13 creator wallets. 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.3% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

Liquidity0.0 SOL
Read from chain2026-11-06 00:38 UTC, just now

What this launch claimed to be

The picture this launch published at birth
Nameaaaaaaaaaaaaaaaa
Metadata heldsha256 ebff830c6be222651eaf8f0787e11b2a0dd32f3293983b5354e26777bc9077df · 264 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 52428e9b9103012797eae3730fcd7485add8a9d07e971639f9a8c6b284facd6b · 25,322 bytes

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