Hachiko
The creator took 23% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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 took 22.6% of supply at launch.
noteOnly 4.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 09:37 UTC |
| Creator | 59SWBzUSSJ9G4KQhKfw7LkPJQ3KDMQj5ZyEaG7wf7T78 |
| Creator took | 22.6% of supply in the first block |
| Outside buyers | 718 distinct wallets, not counting the creator, bought on the bonding curve: 103 within the first 30s, 11 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 | not while we watched |
| Recorded from | 2YwWDZEj1CipYS8DhuoTje… slot 452,249,345
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 09:37:44 UTC Slot 452,249,345, which is the chain's own clock for this moment. |
| Creation block | 11 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 103 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 10:13:30 UTC +35m 46s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 10:13:30 UTC +35m 46s
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 4 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 52 launches from 25 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 2 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 4.9 SOL |
| Read from chain | 2026-10-02 14:45 UTC, just now |
What this launch claimed to be
| Name | Hachiko the Stickdog |
| Metadata held | sha256 b109c6ab666958e50db5df1be1b86cf7aa44ec8bc1ec12d459fc6f4d8c23ce69 · 367 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-10-02 09:37 UTC. |
| Picture held | sha256 de7e78e4e82cb980ad4471f7be3ae102ff0ea32dff0b69631959bea26749e639 · 4,584 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 09:37 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.