1,902,056 launches on record
Coverage from 2 Sep 2026
Archive read 14 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Pro

币安人

The curve completed in the same batch of events as the launchRead 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. We did not record its creation transaction, so these figures rest on our observation at the time rather than on a citation you can follow. Not a prediction and not advice.

3jjcQ9BkTMFEpbtSXoN83CzgkMe9aLCZeX2W4P36aQc4 Solscan pump.fun

Cite this record as: Chain of Title, 币安人 (我是币安人), mint 3jjcQ9BkTMFEpbtSXoN83CzgkMe9aLCZeX2W4P36aQc4, observed at creation 2026-09-02 15:58 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/3jjcQ9BkTMFEpbtSXoN83CzgkMe9aLCZeX2W4P36aQc4

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 0s after launch.

At launch

Created2026-09-02 15:58 UTC
Creator2WMKeGgTYfjXgsSkiejaj2oNbAxeoiEVezoa796Fqt84
Creator took0.0% of supply in the first block
Outside buyersunknown 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, 6 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.
Graduated0 min after launch
Curve on chainComplete. We read the bonding curve account 35.1 days ago and it was finished. Checked 2026-09-09 23:04 UTC.
Creator soldnot while we watched
Recorded fromNot recorded. This launch predates our keeping the creation transaction (2026-09-09), and its trade rows had been pruned by retention before the backfill could recover the signature from them. The figures above stand on our own observation alone, which is weaker than a citation, and we would rather say so than leave the gap unmarked.
Not recordedcurve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
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.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-09-02 15:58:59 UTC
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-09-02 15:58:59 UTC +0s
Confirmed against the venue's own completion state.
Highest price seen2026-09-02 15:58:59 UTC +0s
4.109e-7 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. 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 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 tickerOn 3 launches from 3 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, 87.3% wear one that more than one creator wallet has launched. See this ticker's page →

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

Name我是币安人
Description我是币安人
Metadata heldsha256 eadb35fdcf3a943417d4ad3179a8d544594490103ab81f9a17b90f021974cfa1
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-09-23 00:58 UTC.
PictureNot captured, so we cannot show what it published. That is our storage budget, not a finding about the launch.

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