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: 4ffb7f309bc30c998b1398a70f69eb3a7842f1ce349a23390639f51056802fc0
Tx prefix hash: 24413248b88a073f9622993933d7654095a2bb04725293b94c9db8117f9cd1fb
Tx public key: 7208eac4f69c4285a40b4fe42cd429cd3f7c9c0687ec81fed5ca7ac1c3d76a19
| Timestamp: 1779957923 | Timestamp [UTC]: 2026-05-28 08:45:23 | Age [y:d:h:m:s]: 00:011:18:04:25 |
| Block: 3722 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4198 | RingCT/type: yes/0 |
| Extra: 017208eac4f69c4285a40b4fe42cd429cd3f7c9c0687ec81fed5ca7ac1c3d76a1902090000000726697be300 | ||
1 output(s) for total of 34.935543810709 HMNY
| stealth address | amount | amount idx | tag |
| 00: 525716cce421bb32b3a051336d7b85e55ba191afe44e417814ed0f513c1c9370 | 34.935543810709 | 4505 of 0 | <12> |
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": 3782,
"vin": [ {
"gen": {
"height": 3722
}
}
],
"vout": [ {
"amount": 34935543810709,
"target": {
"tagged_key": {
"key": "525716cce421bb32b3a051336d7b85e55ba191afe44e417814ed0f513c1c9370",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 114, 8, 234, 196, 246, 156, 66, 133, 164, 11, 79, 228, 44, 212, 41, 205, 63, 124, 156, 6, 135, 236, 129, 254, 213, 202, 122, 193, 195, 215, 106, 25, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}