← all tokens
9MjRHK7iFSDco7EYMuU5L9sp9a9gPr7jTudzgTdNpump
The mintslot 451,434,211
token programTokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
supply998594230725281
decimals6
mint authoritynull: revoked
freeze authoritynull: revoked
Fee configurationslot 451,434,211
0.0080 SOLPENDING
8,017,921 lamports · read at slot 451,434,211
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 accountHcfhhpxMBRuEwvFMQ4Z36652pZBAh9VuUHXE9y1NYcR6
adminBT2sdwJeDWqXNUNBJwtKWBD7RjquACfjo1rT9vpZLUSA
byte 751: shown, not interpreted
shareholders2
holder 0BT2s…LUSA · 75.00% (7500 bps)
holder 1Ad9y…GULc · 25.00% (2500 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.