Vikings
The creator took 27% of supply at 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. 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 took 26.6% of supply at launch.
noteOnly 2.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-28 16:28 UTC |
| Creator | D9TJSn3jpuSZPzUxwhFUAHEC1wVf5vbfEsMPNvKaZC4h |
| Creator took | 26.6% of supply in the first block |
| Outside buyers | 41 distinct wallets, not counting the creator, bought on the bonding curve: 11 within the first 30s, 3 bundled into the creation block. |
| Graduated | 33 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 | 8FTRYM65jCgeSVfYFJS9Ww… slot 451,372,663
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-28 16:28:08 UTC Slot 451,372,663, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 11 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-28 17:01:03 UTC +32m 54s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-28 17:47:32 UTC +1h 19m 24s
0.000e+0 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. |
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 | No other launch we hold a picture for used this one. |
| This ticker | On 3 launches from 3 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.5 SOL |
| Read from chain | 2026-09-29 21:45 UTC, just now |
What this launch claimed to be
| Name | Vikings |
| Description | Have a wonderful week, Vikings ⚔️ |
| Metadata held | sha256 e81592ffe2446172876c7d1f8e7b1ff7a147139ab5b99c9a7f0ec45169cc60ca · 315 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-29 16:30 UTC. |
| Picture held | sha256 8688cb790c51a8850ab0bc821cfe2150e81f205bf579f71069e5d126d0a0a2a7 · 176,849 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-28 16:28 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.