VAMPIRE
Checked, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; 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.
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.
noteOnly 0.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 15:59 UTC |
| Creator | 4Wtx7kZvL4LkxZ8Ma8oM2uopVZ7RMdNJUFBB4x2QRFh4 |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 998 distinct wallets, not counting the creator, bought on the bonding curve: 218 within the first 30s, 6 bundled into the creation block. |
| Graduated | 6 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not while we watched |
| Recorded from | 41fo7YhEcYU1ShTt4t62cQ… slot 451,689,092
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 15:59:34 UTC Slot 451,689,092, which is the chain's own clock for this moment. |
| Creation block | 6 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 218 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 completed | 2026-09-29 16:05:50 UTC +6m 15s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 16:05:54 UTC +6m 20s
4.109e-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 picture | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 11 launches from 10 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 0.9 SOL |
| Read from chain | 2026-10-01 01:53 UTC, just now |
What this launch claimed to be
| Name | VAMPIRE |
| Metadata held | sha256 e2d2349dc057204546c0b7ef7d9b838f3a5b3f1d19b8fee845c312f4b5ab5583 · 256 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-read | Byte-identical to the launch-time capture when re-read 2026-09-30 16:00 UTC. |
| Picture held | sha256 9cd748d5b962b720ddce7ae88aba7e36e9e1d86df25d26237cb57e963770e74b · 9,965 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 15:59 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.