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: b364ac32d97f53ecf95ff6d76a2605dcd09451cc4d35debd2ba8add80bef3d60
Tx prefix hash: 94415865416cbbdb67167853f0aeb7f60905b05074c4624babc4393dd299c163
Tx public key: 23cae7efc2c0d891ec4e412c471b0af950a4b42e9c289652f9905f799b15bff1
| Timestamp: 1779936660 | Timestamp [UTC]: 2026-05-28 02:51:00 | Age [y:d:h:m:s]: 00:011:22:44:57 |
| Block: 3444 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4442 | RingCT/type: yes/0 |
| Extra: 0123cae7efc2c0d891ec4e412c471b0af950a4b42e9c289652f9905f799b15bff102090000000126697be300 | ||
1 output(s) for total of 34.954073065208 HMNY
| stealth address | amount | amount idx | tag |
| 00: a3004065435aba4cc8f24dfbf301d8a649b0f3581d2bd795b8db4bc6fc526895 | 34.954073065208 | 4161 of 0 | <9b> |
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": 3504,
"vin": [ {
"gen": {
"height": 3444
}
}
],
"vout": [ {
"amount": 34954073065208,
"target": {
"tagged_key": {
"key": "a3004065435aba4cc8f24dfbf301d8a649b0f3581d2bd795b8db4bc6fc526895",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 35, 202, 231, 239, 194, 192, 216, 145, 236, 78, 65, 44, 71, 27, 10, 249, 80, 164, 180, 46, 156, 40, 150, 82, 249, 144, 95, 121, 155, 21, 191, 241, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}