Content pfp
Content
@
0 reply
1 recast
2 reactions

Ben | 0443.eth pfp
Ben | 0443.eth
@nvben
Little technical question, trying to understand why I'm seeing a transfer of 10287180257164609 in the raw data but 102,871,802,571.64607 in the formatted version. https://explorer.solana.com/tx/Cm1SkXFqwfSiTjME9hWLCR2tmWL3xJ78rx2ApKnfei5ufERAvSiU74hHSdfNTQSy6f7crTPpHY4emc3m3oK11jX
2 replies
0 recast
0 reaction

Algo Rhythmic pfp
Algo Rhythmic
@algorhythmic
Units of BONK only go out 5 decimal places. The raw is the the total sub-units of BONK, whereas the formatted places the decimal properly for you. When you launch a token, it's up to you how many decimal places you want to permit. Here is an example (wallet login req): https://fluxbeam.xyz/app/tools/token_create
2 replies
0 recast
1 reaction

Algo Rhythmic pfp
Algo Rhythmic
@algorhythmic
If you look at the BONK contract address in solscan, it'll tell you how many decimals it observes (https://solscan.io/token/DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263)
0 reply
0 recast
0 reaction

Ben | 0443.eth pfp
Ben | 0443.eth
@nvben
Totally understand, what is confusing is that the last 5 digits of the raw value are 64609 while the last 5 digits of the formatted value are 64607. The thing is, every block explorer and API is reporting this as xxxxx.64607 when it would seem like the value should in fact be xxxxx.64609.
1 reply
0 recast
0 reaction