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: db562df278d5b26934faa63dee5a7ee7880e7f9efa3eec9f0ac9870c77fc879a
Tx prefix hash: b9550a35f57072917845a18c3395c63631d21a394bc6b6b223f8870af69b5357
Tx public key: 6840d51179650c46bfc8634eec67d45360f2d61aa59dc00c98c06d99ff12a7d3
| Timestamp: 1779774003 | Timestamp [UTC]: 2026-05-26 05:40:03 | Age [y:d:h:m:s]: 00:018:05:22:13 |
| Block: 2051 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6694 | RingCT/type: yes/0 |
| Extra: 016840d51179650c46bfc8634eec67d45360f2d61aa59dc00c98c06d99ff12a7d302090000000326697be300 | ||
1 output(s) for total of 35.054453396849 HMNY
| stealth address | amount | amount idx | tag |
| 00: f50f8d57bf9f729589fbd7a06c65bffc2814b94e62355887c837734881262807 | 35.054453396849 | 2345 of 0 | <07> |
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": 2111,
"vin": [ {
"gen": {
"height": 2051
}
}
],
"vout": [ {
"amount": 35054453396849,
"target": {
"tagged_key": {
"key": "f50f8d57bf9f729589fbd7a06c65bffc2814b94e62355887c837734881262807",
"view_tag": "07"
}
}
}
],
"extra": [ 1, 104, 64, 213, 17, 121, 101, 12, 70, 191, 200, 99, 78, 236, 103, 212, 83, 96, 242, 214, 26, 165, 157, 192, 12, 152, 192, 109, 153, 255, 18, 167, 211, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}