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: dfe78bd45c69d74018cd50014778ee1d519a53e903950b774287567ec3240c28
Tx prefix hash: 20cd662af9c2deaa6403b14c76cde40456d2174ddb71bacc6817cda154d5c9a3
Tx public key: e53e8affeda5e873eff2263e1cba594103f5dddf8acece448cc9c681ba3eab00
| Timestamp: 1779641073 | Timestamp [UTC]: 2026-05-24 16:44:33 | Age [y:d:h:m:s]: 00:015:10:05:15 |
| Block: 1319 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6601 | RingCT/type: yes/0 |
| Extra: 01e53e8affeda5e873eff2263e1cba594103f5dddf8acece448cc9c681ba3eab00020900000001ba6d17be00 | ||
1 output(s) for total of 35.096033604886 HMNY
| stealth address | amount | amount idx | tag |
| 00: 592f66e3040b1d472f9f5ef3e184c98150a6c4afd096f994e0f6e2150bd6cf8f | 35.096033604886 | 1467 of 0 | <c6> |
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": 1379,
"vin": [ {
"gen": {
"height": 1319
}
}
],
"vout": [ {
"amount": 35096033604886,
"target": {
"tagged_key": {
"key": "592f66e3040b1d472f9f5ef3e184c98150a6c4afd096f994e0f6e2150bd6cf8f",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 229, 62, 138, 255, 237, 165, 232, 115, 239, 242, 38, 62, 28, 186, 89, 65, 3, 245, 221, 223, 138, 206, 206, 68, 140, 201, 198, 129, 186, 62, 171, 0, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}