← all tokens
447Pwhrc7c5gq5qt5VoyoFeLMMBQjiFLmejSqLwZpKs7
The mintslot 451,433,949
token programTokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
supply1000000000000000
decimals6
mint authoritynull: revoked
freeze authoritynull: revoked
Fee configurationslot 451,433,949
unreadPENDING
the balance could not be read. This is not a zero
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 account9cZZFv19SXLH9qwPcCHUfgDSBsSKpoPSu4nBmLWwffet
adminDEX3nbA4DaiWc5qxG9HLS71k9baX1ijDJP1eumv7vZEB
byte 751: shown, not interpreted
shareholders2
holder 02G7G…Nse1 · 30.00% (3000 bps)
holder 18tWV…ZNP4 · 70.00% (7000 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.