What this launch shares with other launches
Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.
Its own first blocks
Also recorded, and not part of the finding above: this picture is on 1 other launch, all of them this same creator's. 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, 12.9% of the launches whose picture we hold carry one only their own creator reused. 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.
At launch
| Created | 2026-11-19 01:40 UTC |
| Creator | S991ngFqtvzupXJ7GJ4e6XmeLoo73fBh6mRgacxbVaV |
| Creator took | 12.5% of supply in the first block |
| Outside buyers | 5 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: 0 within the first 30s, 4 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. |
| Graduated | 4.9 h after launch |
| Curve 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 | not while we watched |
| Recorded from | 5CMoaJNE8NBX8zNErvGyCL… slot 471,155,155
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-19 01:40:54 UTC Slot 471,155,155, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | No buyer, 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. |
| Highest price seen | 2026-11-19 03:14:42 UTC +1h 33m 48s
7.125e-8 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. |
| Curve completed | 2026-11-19 06:34:17 UTC +4h 53m 24s Confirmed: a PumpSwap pool was found for it. |
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. |
Pool
| Liquidity | 51.5 SOL |
| Read from chain | 2026-11-19 15:33 UTC, just now |
What this launch claimed to be
| Name | Nikumaru |
| Description | “Nikumaru” is one of the official candidate names. The pygmy hippo calf was born at Higashiyama Zoo on August 11, 2026. In 2023, Koyuri lost her first calf just one day after birth. Three years later, Koyuri was given a second chance. The calf’s father is Mirai — Japanese for “future.” If the calf continues to thrive, it will be the first pygmy hippo successfully raised at Higashiyama in 32 years. A second chance. A future born. |
| Metadata held | sha256 3b3798c81e6218fbf5fac3ab7c42f2c813cf3de6b37299045b447deac79328a7 · 767 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 9afc88d82d57b237a39d771d246ed774c42e3f89c1ad736994a220050f67c4c1 · 1,241,472 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-19 01:40 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.