3,225,025 launches on record
Coverage from 2 Sep 2026
Archive read 07:33 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

Capiboo

The curve completed 28s 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 22 other launches from 3 creator wallets in all, 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, 55.4% 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.

5KAzp8cQKXZCBtbrk7FaX7GFsGuDzeyRudY2f3BQpump Solscan pump.fun

Cite this record as: Chain of Title, Capiboo, mint 5KAzp8cQKXZCBtbrk7FaX7GFsGuDzeyRudY2f3BQpump, observed at creation 2026-11-06 07:43 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/5KAzp8cQKXZCBtbrk7FaX7GFsGuDzeyRudY2f3BQpump

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.

noteThe creator took 42.7% of supply at launch.
findingIt left the curve 28s after launch.
noteThe creator sold while we were watching.
noteOnly 1.3 SOL of liquidity was in the pool just now.

At launch

Created2026-11-06 07:43 UTC
CreatorAXRZB7qUJKKH6Xmw8xkM9iBg1iZafqV1z1UB7RvijrYF
Creator took42.7% of supply in the first block
Outside buyers14 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.
Graduated0 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 soldyes
Recorded from67Cd3awHrwSMHyFLz3EsWc… slot 466,029,444
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-11-06 07:43:06 UTC
Slot 466,029,444, which is the chain's own clock for this moment.
Creation block4 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-11-06 07:43:33 UTC +28s
Confirmed: a PumpSwap pool was found for it.
Thirty seconds in14 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.
Highest price seen2026-11-06 08:01:30 UTC +18m 24s
6.926e-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 22 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 55.4% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 29 launches from 4 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 →
This documentThe same launch document, byte for byte, as 21 other launches, across 3 creator wallets in all. Across the archive, 32.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator18 earlier launches, 3 confirmed complete on chain. Across the archive, 70.5% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 3 other creator wallets, across 4 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.8% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Who took the curve

One transaction bought 64 SOL of this curve, 0 min after launch, from a wallet other than the creator's. The wallet and the transaction →

Pool

Liquidity1.3 SOL
Read from chain2026-11-06 11:43 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameCapiboo
DescriptionI do nothing all day. Then I rest.
Metadata heldsha256 b19bdb912be58aa27a815bed928a866ad34c86726e179255502cac7f202530b6 · 298 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 43084d70e43e308da07f2a33d5190e2f47637929b41bd0653e9f6b1a29e6ece4 · 714,518 bytes

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