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: 6846f7c86c48e9fe5a47ca9be5cd6b83adcbb093aa461214428b555380fbfb4c
Tx prefix hash: 3e30967a87b0a6618e07e5e7ea978e4f778da08b6510c7098c3d569e99c59cac
Tx public key: 30f5b53549034e5b19a20ddcf4d6740aa00c9f174d6698fbfcdab14fee8528c1
| Timestamp: 1779630596 | Timestamp [UTC]: 2026-05-24 13:49:56 | Age [y:d:h:m:s]: 00:015:13:48:54 |
| Block: 879 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7063 | RingCT/type: yes/0 |
| Extra: 0130f5b53549034e5b19a20ddcf4d6740aa00c9f174d6698fbfcdab14fee8528c1020900000001ba6d17be00 | ||
1 output(s) for total of 35.125499759302 HMNY
| stealth address | amount | amount idx | tag |
| 00: f0946e1de7e7437f127075ad4a3abb4c7412b5c6598fc61334ecde090386fc7f | 35.125499759302 | 1011 of 0 | <0b> |
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": 939,
"vin": [ {
"gen": {
"height": 879
}
}
],
"vout": [ {
"amount": 35125499759302,
"target": {
"tagged_key": {
"key": "f0946e1de7e7437f127075ad4a3abb4c7412b5c6598fc61334ecde090386fc7f",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 48, 245, 181, 53, 73, 3, 78, 91, 25, 162, 13, 220, 244, 214, 116, 10, 160, 12, 159, 23, 77, 102, 152, 251, 252, 218, 177, 79, 238, 133, 40, 193, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}