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: ebf340a3e79f65973d3413c5d147ba78da3882228969efc8c054d257ba057ff0
Tx prefix hash: 960fa1698bc97d1a300e835c68a213a8e84fd46b958a6c9b153495c70384e1c7
Tx public key: 664e8f82523d9f02f6a69f0c41b15f7f0a4748cc0ca52dd108ab23c30e001337
| Timestamp: 1781018792 | Timestamp [UTC]: 2026-06-09 15:26:32 | Age [y:d:h:m:s]: 00:006:01:16:42 |
| Block: 8665 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 80 | RingCT/type: yes/0 |
| Extra: 01664e8f82523d9f02f6a69f0c41b15f7f0a4748cc0ca52dd108ab23c30e001337020900000001e49593ff00 | ||
1 output(s) for total of 34.607718144842 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4086af92ad7b6c98c94e36bc241996c9cb465039cff678cba843693c2559f070 | 34.607718144842 | 10713 of 0 | <70> |
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": 8725,
"vin": [ {
"gen": {
"height": 8665
}
}
],
"vout": [ {
"amount": 34607718144842,
"target": {
"tagged_key": {
"key": "4086af92ad7b6c98c94e36bc241996c9cb465039cff678cba843693c2559f070",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 102, 78, 143, 130, 82, 61, 159, 2, 246, 166, 159, 12, 65, 177, 95, 127, 10, 71, 72, 204, 12, 165, 45, 209, 8, 171, 35, 195, 14, 0, 19, 55, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}