ia
Checked, no markers foundWe watched this launch and checked it against every marker we record. None of them is present: the creator kept 4.0%, 313 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. A statement about what we checked, not a judgement about the token.
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.
At launch
| Created | 2026-09-30 19:24 UTC |
| Creator | 7SjCqTb2NNrdkVNQw4NMpG9i6ZBdsrR5MU6KZ5PsGgY7 |
| Creator took | 4.0% of supply in the first block |
| Outside buyers | 313 distinct wallets, not counting the creator, bought on the bonding curve: 105 within the first 30s, 8 bundled into the creation block. |
| Graduated | 4.8 h after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not while we watched |
| Recorded from | 2ckNiiP3Uj1XPqbk7XzfmZ… slot 452,057,808
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 19:24:42 UTC Slot 452,057,808, which is the chain's own clock for this moment. |
| Creation block | 8 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 105 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 00:10:05 UTC +4h 45m 23s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 00:10:05 UTC +4h 45m 23s
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 6 launches from 5 creator wallets, including this one. See them → |
Pool
| Liquidity | 83.3 SOL |
| Read from chain | 2026-10-01 06:08 UTC, just now |
What this launch claimed to be
| Name | inu/acc |
| Metadata held | sha256 2c7b19651180c99ad8e28ee17384a3a7a447840b3d315a8107e1d69aed7d7c1d · 187 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 146709a3e89e5b8a987dc86322e0e1986551675c46d0324982356b353efa3f27 · 322,058 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 19:24 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.