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: 4457b73e82b684067a2cffff75ed6932e9793b089c92268dd68540c43fb1be61
Tx prefix hash: 756c68d6ede9a761d53bedeb949df0e8dc190ec2af8acb7780baa29240d2855a
Tx public key: 71f13dba3e472811cb0cb3bbf4d2b962f2d0597d518db26264ce9f05b9194420
| Timestamp: 1779633010 | Timestamp [UTC]: 2026-05-24 14:30:10 | Age [y:d:h:m:s]: 00:015:11:05:47 |
| Block: 972 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6914 | RingCT/type: yes/0 |
| Extra: 0171f13dba3e472811cb0cb3bbf4d2b962f2d0597d518db26264ce9f05b9194420020900000001ba6d17be00 | ||
1 output(s) for total of 35.119269624561 HMNY
| stealth address | amount | amount idx | tag |
| 00: 94bf6c30c5b0d67b05d514a3a5c2b39f493c6deec0e3337c6dc44bfda99d9ec3 | 35.119269624561 | 1108 of 0 | <0c> |
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": 1032,
"vin": [ {
"gen": {
"height": 972
}
}
],
"vout": [ {
"amount": 35119269624561,
"target": {
"tagged_key": {
"key": "94bf6c30c5b0d67b05d514a3a5c2b39f493c6deec0e3337c6dc44bfda99d9ec3",
"view_tag": "0c"
}
}
}
],
"extra": [ 1, 113, 241, 61, 186, 62, 71, 40, 17, 203, 12, 179, 187, 244, 210, 185, 98, 242, 208, 89, 125, 81, 141, 178, 98, 100, 206, 159, 5, 185, 25, 68, 32, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}