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: b4ef43f0ace7ee419654e0a334ee310a9c6a23e88f18d292d10abcc64837ac5f
Tx prefix hash: af6b349391ce5835ca723a2944f350f1f15ec1af7de9e552ad04218d19278fd7
Tx public key: 5376104e2f709163f24a6fb376b1d2be52faaea5ea57d052127373e38ec410e8
| Timestamp: 1779948916 | Timestamp [UTC]: 2026-05-28 06:15:16 | Age [y:d:h:m:s]: 00:011:18:31:31 |
| Block: 3595 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4291 | RingCT/type: yes/0 |
| Extra: 015376104e2f709163f24a6fb376b1d2be52faaea5ea57d052127373e38ec410e802090000000526697be300 | ||
1 output(s) for total of 34.944007395059 HMNY
| stealth address | amount | amount idx | tag |
| 00: 345e8b7b6b8720401062f3b1743544383ff5847fe264f541d55609c1789f033b | 34.944007395059 | 4340 of 0 | <2a> |
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": 3655,
"vin": [ {
"gen": {
"height": 3595
}
}
],
"vout": [ {
"amount": 34944007395059,
"target": {
"tagged_key": {
"key": "345e8b7b6b8720401062f3b1743544383ff5847fe264f541d55609c1789f033b",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 83, 118, 16, 78, 47, 112, 145, 99, 242, 74, 111, 179, 118, 177, 210, 190, 82, 250, 174, 165, 234, 87, 208, 82, 18, 115, 115, 227, 142, 196, 16, 232, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}