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: 7b68cb682d5d21219136f38d7c54cea942c19ab5a95a77e49af637443bb6f32a
Tx prefix hash: 65d0d49f5bff41f9b94151befa153051575e7b46121a8260aea5d6e1c987dc7e
Tx public key: d79d56ce5333c8a25db500a5b3e0ffb18f98d6a09e8ef520ee1f8e80e0ca47c6
| Timestamp: 1779717545 | Timestamp [UTC]: 2026-05-25 13:59:05 | Age [y:d:h:m:s]: 00:020:18:20:30 |
| Block: 1685 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7060 | RingCT/type: yes/0 |
| Extra: 01d79d56ce5333c8a25db500a5b3e0ffb18f98d6a09e8ef520ee1f8e80e0ca47c6020900000001ba6d17be00 | ||
1 output(s) for total of 35.071541955159 HMNY
| stealth address | amount | amount idx | tag |
| 00: 374a9455c8aca531379fe546283029f10a5495b7cf57526d8063cd54dda5ef72 | 35.071541955159 | 1852 of 0 | <04> |
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": 1745,
"vin": [ {
"gen": {
"height": 1685
}
}
],
"vout": [ {
"amount": 35071541955159,
"target": {
"tagged_key": {
"key": "374a9455c8aca531379fe546283029f10a5495b7cf57526d8063cd54dda5ef72",
"view_tag": "04"
}
}
}
],
"extra": [ 1, 215, 157, 86, 206, 83, 51, 200, 162, 93, 181, 0, 165, 179, 224, 255, 177, 143, 152, 214, 160, 158, 142, 245, 32, 238, 31, 142, 128, 224, 202, 71, 198, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}