For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 797fe33b75a69e2877913681145b57f919574f99906325edea9439c915887422
Tx prefix hash: af32c687de317661af84c088000eda38a727c64dc4cbfcde80943d471dc94df4
Tx public key: 0e4fdf2db4838a916053fb97a86a24a9368cc8312c6dcdcbb7c4253a60bf8924
| Timestamp: 1780068605 | Timestamp [UTC]: 2026-05-29 15:30:05 | Age [y:d:h:m:s]: 00:010:11:19:43 |
| Block: 4620 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3280 | RingCT/type: yes/0 |
| Extra: 010e4fdf2db4838a916053fb97a86a24a9368cc8312c6dcdcbb7c4253a60bf892402090000000126697be300 | ||
1 output(s) for total of 34.875757402333 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6ce79fbd3e7661a93941d688c4b0fffe3dfa225857a6db92869df533c94c08c7 | 34.875757402333 | 5801 of 0 | <c8> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 4680,
"vin": [ {
"gen": {
"height": 4620
}
}
],
"vout": [ {
"amount": 34875757402333,
"target": {
"tagged_key": {
"key": "6ce79fbd3e7661a93941d688c4b0fffe3dfa225857a6db92869df533c94c08c7",
"view_tag": "c8"
}
}
}
],
"extra": [ 1, 14, 79, 223, 45, 180, 131, 138, 145, 96, 83, 251, 151, 168, 106, 36, 169, 54, 140, 200, 49, 44, 109, 205, 203, 183, 196, 37, 58, 96, 191, 137, 36, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}