VAMPIRE
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
noteThe creator sold while we were watching.
noteOnly 0.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 18:13 UTC |
| Creator | GrnvRbmTmu9GjQWNPWsJXM7D1J4PzRpeTGqbGXofMum5 |
| Creator took | 3.1% of supply in the first block |
| Outside buyers | 943 distinct wallets, not counting the creator, bought on the bonding curve: 144 within the first 30s, 22 bundled into the creation block. |
| Graduated | 6 min after launch |
| Curve, read on chain | Not 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 sold | yes |
| Recorded from | 2PcTRQUdZ3MB4joH5KfM3k… slot 452,687,544
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 18:13:03 UTC Slot 452,687,544, which is the chain's own clock for this moment. |
| Creation block | 22 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 144 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-10-02 18:19:11 UTC +6m 08s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 18:19:11 UTC +6m 08s
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 5 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 19 launches from 16 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 3 other creator wallets, across 3 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 0.9 SOL |
| Read from chain | 2026-10-03 02:07 UTC, just now |
What this launch claimed to be
| Name | Vampire |
| Description | A vampire that picks the wallet itself and drinks 1% of every buy. Half to holders, the rest burns. |
| Metadata held | sha256 97ff95e96e3dee6d1d39f8471699673716be5c90dd5f84c809825d713ab23caf · 368 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 5226f13ed5add3b02bc0f5212afd228295d4c643dd8ea896347d8a1b282d7d86 · 19,171 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 18:13 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.