HI
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.
noteThe creator sold while we were watching.
noteOnly 0.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 14:56 UTC |
| Creator | 9NcZqc8geXsFEZ7ccFfzrV2EJHNnt1YoEUnckthWvL5d |
| Creator took | 1.2% of supply in the first block |
| Outside buyers | 270 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 4 bundled into the creation block. |
| Graduated | 36 min 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 | yes |
| Recorded from | 57oAsY5Zr92RZ5nLUiogwW… slot 452,320,824
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 14:56:28 UTC Slot 452,320,824, 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 | 4 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 15:32:49 UTC +36m 21s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 15:32:49 UTC +36m 21s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 900 launches from 465 creator wallets, including this one. See them → |
Pool
| Liquidity | 0.9 SOL |
| Read from chain | 2026-10-02 07:10 UTC, just now |
What this launch claimed to be
| Name | Hell o Inu |
| Metadata held | sha256 61cb4762f9b2922a838b2609ab9c24b4efdc8a209befdba6a5f1c544caa4d492 · 270 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 f74625e898893de95c532dce44454d69f093e48b3f08d919a6c73e40d28b49a4 · 1,407,455 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 14:56 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.