Launch
← all tokens

try BOAR · ELON

LITERALLY SLAM THE SCAM DAY SCAM

8SqoC2pzD4jG3F4XBsTsZKmfpQP759Y39fYEEaFFpump

no picture: the metadata URI could not be fetched

The mintslot 449,473,112
token programTokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
supply1000000000000000
decimals6
mint authoritynull — revoked
freeze authoritynull — revoked
Fee configurationslot 449,473,112
0.0080 SOLPENDING

8,017,920 lamports · read at slot 449,473,112

Held by the configuration account. It is addressed to nobody and nobody has taken it, so it is not claimable and certainly not received.

config accountGneu56USV5JC5Jnmd6kF6eZV8DmbiEBL4EGBfCxTmLFc
adminGvpePLZFAq3gSzHVTywR6kwVtgdQxttDbN4y1iPPVXSU
byte 750 — shown, not interpreted
shareholders1
holder 09SyS…DzGg · 100.00% (10000 bps)
shares add up to10000 bps — the whole fee

These were printed as raw bytes until 2026-09-22, with a note saying the share reading was wrong: they read 10000 in 3,874 of 3,880 single-holder configs, yet 0 of 120 multi-holder configs summed to 10000. The control was right to stop the claim and wrong about why. The field was always basis points — the stride was wrong. An entry is 34 bytes, not 40, so every holder after the first was being read six bytes inside the previous one’s share. Re-read at 34, 24 of 24 multi-holder configs sum to exactly 10000.