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: e7c6f088af5d4c1c5610017711d547f2bcabe2fbc67ae042f07de68f34305e7e
Tx prefix hash: 7369d18a9ef8f41a91eb2f0dce8f64d1d442df06813fa106312d527adc0993f3
Tx public key: 8bc3b1085f1c8b38f5366ef8ad2bff78a754745286f32561c2a90e919c2ced40
| Timestamp: 1779716162 | Timestamp [UTC]: 2026-05-25 13:36:02 | Age [y:d:h:m:s]: 00:014:13:04:34 |
| Block: 1650 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6246 | RingCT/type: yes/0 |
| Extra: 018bc3b1085f1c8b38f5366ef8ad2bff78a754745286f32561c2a90e919c2ced40020900000004ba6d17be00 | ||
1 output(s) for total of 35.073883313559 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7cf24ff57eefdd66b1793aea948e00dc775b150a8de6c4402d1f9eade57efbea | 35.073883313559 | 1812 of 0 | <87> |
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": 1710,
"vin": [ {
"gen": {
"height": 1650
}
}
],
"vout": [ {
"amount": 35073883313559,
"target": {
"tagged_key": {
"key": "7cf24ff57eefdd66b1793aea948e00dc775b150a8de6c4402d1f9eade57efbea",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 139, 195, 177, 8, 95, 28, 139, 56, 245, 54, 110, 248, 173, 43, 255, 120, 167, 84, 116, 82, 134, 243, 37, 97, 194, 169, 14, 145, 156, 44, 237, 64, 2, 9, 0, 0, 0, 4, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}