AI
The curve completed 52s 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 52s after launch.
noteOnly 3.2 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 23:14 UTC |
| Creator | Da2Q3qwZSeh3mmDPJoT9xW7LApzLchrP4VmzyAH75gaN |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 253 distinct wallets, not counting the creator, bought on the bonding curve: 151 within the first 30s, 9 bundled into the creation block. |
| Graduated | 1 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 | 66R7vLcHfAg4VYfXQwL82g… slot 452,431,969
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 23:14:05 UTC Slot 452,431,969, 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 | 151 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 23:14:57 UTC +52s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 23:14:57 UTC +52s
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 → |
| This ticker | On 3,264 launches from 1,888 creator wallets, including this one. See them → |
Pool
| Liquidity | 3.2 SOL |
| Read from chain | 2026-10-02 03:47 UTC, just now |
What this launch claimed to be
| Name | Axiom Inu |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 c3f2f34635a5355652bc06887f0bba042a587228021486d248526556badaa25b · 288 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 dde5863a8aab68a82468bf8a8575060dafa83116f95c7d978b3639562f2f781a · 43,060 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 23:14 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.