Launch record · observed at creation 2026-11-07 04:58 UTC

HARAM

HARAMBE

3kNwhPwxkbz1Q8mbFZcmPVTPLLxiZxsZdBL5zhfpump2 Copy Solscan

Also recorded, and not part of the finding above: this picture is on 2 other launches from 3 creator wallets in all. 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, 56.2% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.

At launch

Created	2026-11-07 04:58 UTC
Creator	HdPvXDqdFPecugsoZZS5LvFY9Ywjtq5Ubs5wWP3KVAQx
Creator took	0.0% of supply in the first block
Outside buyers	unknown 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.
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 recorded - this venue's trades do not name the wallet
Recorded from	32WGhHUs5uk2rnY9nvVUT7… slot 466,386,411 The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recorded	curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_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.

Seen before

This picture	On 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them →
This ticker	On 46 launches from 43 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, 89.5% wear one that more than one creator wallet has launched. See this ticker's page →
Files shared with other wallets	Launches by this creator were made with files byte-identical to those of 1 other creator wallet, across 2 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. Across the archive, 64% of launches come from a creator linked to at least one other wallet this way. 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	HARAMBE
Metadata held	sha256 d84cf2753999e6eb62e73fa21689e50293335935361605a21d39a194813f2241 · 245 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 a8d79c93a28f9d1676e39367671502a48a5a5391d638b177aae99db5108e7dce · 68,112 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-11-07 04:58 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.