Nigerinu
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.
noteOnly 2.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 19:20 UTC |
| Creator | GPpA7tLiXzjnAToNci2BoM5NZcxrBCnVGkhEYNGWVhsJ |
| Creator took | 2.6% of supply in the first block |
| Outside buyers | 14 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 9 bundled into the creation block. |
| Graduated | 2.5 h 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 | not while we watched |
| Recorded from | 5zvBLjT8i2nZAt1bgZ3C1S… slot 452,379,684
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 19:20:12 UTC Slot 452,379,684, which is the chain's own clock for this moment. |
| Creation block | 9 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 5 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-01 21:49:20 UTC +2h 29m 08s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 21:49:20 UTC +2h 29m 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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
Pool
| Liquidity | 2.0 SOL |
| Read from chain | 2026-10-02 03:09 UTC, just now |
What this launch claimed to be
| Name | Niger Inu |
| Metadata held | sha256 02d3d9a76c0cf520ee872cf2a02c90fc9015fb87691f0765891ed073ea65c43f · 334 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 0890fe04020db671f2267a487f273815a717e90417da76aa79b2d82eb0c068fd · 123,669 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 19:20 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.