BOT
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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.
noteOnly 1.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 04:18 UTC |
| Creator | 5fg4i8JZQPuBJTroV8vv5yeFJWq8hhxZQa3kiVm7fzyf |
| Creator took | 15.1% of supply in the first block |
| Outside buyers | 152 distinct wallets, not counting the creator, bought on the bonding curve: 72 within the first 30s, 2 bundled into the creation block. |
| Graduated | 2 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 8.3 h ago and it was finished. Checked 2026-10-02 04:31 UTC. |
| Creator sold | not while we watched |
| Recorded from | KDpPTGt36ufuL92CECWPSr… slot 452,500,317
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 04:18:58 UTC Slot 452,500,317, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 72 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-02 04:21:18 UTC +2m 21s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 04:21:18 UTC +2m 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 | On 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 456 launches from 331 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 1 earlier launch, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 1.5 SOL |
| Read from chain | 2026-10-02 12:51 UTC, just now |
What this launch claimed to be
| Name | Botcoin |
| Metadata held | sha256 65a7dff74a95c4af4fa9cb2ba22fc84f4facb7989d75ef41358f9dbe35056875 · 188 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 3d794a01bc4975043425d6e5f7c84e9bd83feb4f6db9b1f496b8d6688b83c9bf · 286,256 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 04:19 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.