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: 870f9cb55b53a124c3e001d92cfcd5775d3d9d4d7d047c8ef6e655b7e7426d75
Tx prefix hash: 49c3a69d3837777671afae39219390dbb86d6426b00576c74ad445888937264f
Tx public key: f7fd350ee8afd630f1237a02e033d68139635af4c5ba2671b28500f172071e20
| Timestamp: 1781006241 | Timestamp [UTC]: 2026-06-09 11:57:21 | Age [y:d:h:m:s]: 00:006:02:55:31 |
| Block: 8554 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 191 | RingCT/type: yes/0 |
| Extra: 01f7fd350ee8afd630f1237a02e033d68139635af4c5ba2671b28500f172071e20020900000001e49593ff00 | ||
1 output(s) for total of 34.615045924718 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9a7ccc368aba1919100cbe36af0407105f363d3ca0a15db773947a0b48d03c44 | 34.615045924718 | 10562 of 0 | <c7> |
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": 8614,
"vin": [ {
"gen": {
"height": 8554
}
}
],
"vout": [ {
"amount": 34615045924718,
"target": {
"tagged_key": {
"key": "9a7ccc368aba1919100cbe36af0407105f363d3ca0a15db773947a0b48d03c44",
"view_tag": "c7"
}
}
}
],
"extra": [ 1, 247, 253, 53, 14, 232, 175, 214, 48, 241, 35, 122, 2, 224, 51, 214, 129, 57, 99, 90, 244, 197, 186, 38, 113, 178, 133, 0, 241, 114, 7, 30, 32, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}