HIM
The curve completed 19s after 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.
findingIt left the curve 19s after launch.
At launch
| Created | 2026-10-02 20:30 UTC |
| Creator | BJdhYodGkFLFV2rYsyBsAyZmAYcfEAQcJZX44yvTtBPi |
| Creator took | 10.0% of supply in the first block |
| Outside buyers | 269 distinct wallets, not counting the creator, bought on the bonding curve: 269 within the first 30s, 5 bundled into the creation block. |
| Graduated | 0 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 | 5KMr7D4f62Ud5C3d4rprqF… slot 452,718,252
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 20:30:38 UTC Slot 452,718,252, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 20:30:57 UTC +19s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 20:30:57 UTC +19s
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. |
| Thirty seconds in | 269 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. |
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 5 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 232 launches from 162 creator wallets, including this one. See them → |
Pool
| Liquidity | 55.5 SOL |
| Read from chain | 2026-10-03 00:59 UTC, just now |
What this launch claimed to be
| Name | Human Interaction Model |
| Description | Can an AI trader out-trade its human? |
| Metadata held | sha256 32795eaf23721c34e5d4c997a42607a92c945e83b2fe25088c8f8c014fc82fdc · 417 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 bf5086814fd479fe33eaf4f7167835bec6eca2c0dd2fdd300036e3b857fe479c · 31,886 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 20:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.