2,416,505 launches on record
Coverage from 2 Sep 2026
Archive read 25 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

Brünnhilde

No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 2 other launches. 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. 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.

HGS5NmToJnbM1wNtRgFhDYmAzy45D23jeT4TC3gZpump Solscan pump.fun

Cite this record as: Chain of Title, Brünnhilde (cat in armor ), mint HGS5NmToJnbM1wNtRgFhDYmAzy45D23jeT4TC3gZpump, observed at creation 2026-10-25 19:19 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/HGS5NmToJnbM1wNtRgFhDYmAzy45D23jeT4TC3gZpump

At launch

Created2026-10-25 19:19 UTC
Creator88wojDs69QNc3h3tEQ2aVj4EFey5iBWQxDuvey5k1rvC
Creator took3.0% of supply in the first block
Outside buyers134 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: 31 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.
Graduatedyes; we did not record when
Curve on chainNot 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 soldnot while we watched
Recorded from3B6pLmuiHsNkMaK8DjU3nB… slot 461,373,317
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-25 19:19:03 UTC
Slot 461,373,317, which is the chain's own clock for this moment.
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in31 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 completedRecorded as complete; we did not record when.
Confirmed against the venue's own completion state.

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 6 launches from 6 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, 88.2% 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

The picture this launch published at birth
Namecat in armor
Metadata heldsha256 dd62e09f330cbf1c8275418393721660aedd3acac0154f04cb0718d1de3d99ac · 267 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 heldsha256 7f760ca31143ffa8a2bf71ee49f55297da2a626bc10d83ea1a0d0d240839c553 · 33,239 bytes

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