VAMPCOIN
Also recorded, and not part of the finding above: this picture is on 1 other launch, all of them this same creator's, and this creator has 179 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, 16.2% of the launches whose picture we hold carry one only their own creator reused. 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.
At launch
| Created | 2026-10-03 06:01 UTC |
| Creator | Ao9D9xuKxhHfTGCd3ZeBPJ3aBRUAicKKnXZ3feH6uuGC |
| Creator took | 9.4% of supply in the first block |
| Outside buyers | 4 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: 4 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. |
| Graduated | not while we were watching |
| Curve on chain | Nothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them. |
| Creator sold | not while we watched |
| Recorded from | 1AKxX4E1FyfmturUAz3J9d… slot 452,846,442
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | snap30_buyers - no thirty-second snapshot was taken, and that snapshot is meaningful only for an observed launch.
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
| Created | 2026-10-03 06:01:24 UTC Slot 452,846,442, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-10-03 06:01:24 UTC +0s
4.560e-8 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 picture | On 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 33 launches from 29 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. See this ticker's page → |
| This creator | 179 earlier launches, 6 confirmed complete on chain, 1 with findings on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 28 other creator wallets, across 91 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. See the linked wallets → |
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 | VAMPCOIN |
| Metadata held | sha256 a20b26b36864a3d843cf6dbc94ffcf0a183392e592569d580c8efb27d7fa8987 · 305 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 held | sha256 adeba5e0f263b5d9f2ebe100dc6f2e15725bdc01d6da30b3a8db32e65ff86f0f · 57,707 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-03 06:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.