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: 6412bc0924367654414473b65e5648ba481f2c8f465a4c9e6bd0e8c36a7019fb
Tx prefix hash: 45448cf342ce4a870426948c8ecf8f4bf392ee6bdaf07bed829fbd0777b8c5e5
Tx public key: a0c8793758464d64a5e57e5bf84f692181612ae7db33019e3d9145f4e00e8a76
| Timestamp: 1779632150 | Timestamp [UTC]: 2026-05-24 14:15:50 | Age [y:d:h:m:s]: 00:015:11:20:07 |
| Block: 939 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6947 | RingCT/type: yes/0 |
| Extra: 01a0c8793758464d64a5e57e5bf84f692181612ae7db33019e3d9145f4e00e8a76020900000001ba6d17be00 | ||
1 output(s) for total of 35.121480191038 HMNY
| stealth address | amount | amount idx | tag |
| 00: 05954c41676c3efc6bdf53095d8dfae2155477a79cd8d1d2f13f0a68f3bd74e0 | 35.121480191038 | 1073 of 0 | <c2> |
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": 999,
"vin": [ {
"gen": {
"height": 939
}
}
],
"vout": [ {
"amount": 35121480191038,
"target": {
"tagged_key": {
"key": "05954c41676c3efc6bdf53095d8dfae2155477a79cd8d1d2f13f0a68f3bd74e0",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 160, 200, 121, 55, 88, 70, 77, 100, 165, 229, 126, 91, 248, 79, 105, 33, 129, 97, 42, 231, 219, 51, 1, 158, 61, 145, 69, 244, 224, 14, 138, 118, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}