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: b5106ae7643dd211425c78883ce7354ae9528fe305ae01b7a95373ca9a29020e
Tx prefix hash: c1f70052604c94bfe05cef3ba19b6095163b9c8530b305fda6642d05431a6856
Tx public key: b08727c0e3dc9532e10af4fa9c2d11976d30e0ddf2b4ff98adace379ffdf84f2
| Timestamp: 1779604829 | Timestamp [UTC]: 2026-05-24 06:40:29 | Age [y:d:h:m:s]: 00:015:20:09:19 |
| Block: 734 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7166 | RingCT/type: yes/0 |
| Extra: 01b08727c0e3dc9532e10af4fa9c2d11976d30e0ddf2b4ff98adace379ffdf84f2 | ||
1 output(s) for total of 35.137818415263 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56713f210074cb6bce7ec8ed9e35dcdd15d2c1b0dd8ef4ecd494a160bd36f1b5 | 35.137818415263 | 864 of 0 | <68> |
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": 794,
"vin": [ {
"gen": {
"height": 734
}
}
],
"vout": [ {
"amount": 35137818415263,
"target": {
"tagged_key": {
"key": "56713f210074cb6bce7ec8ed9e35dcdd15d2c1b0dd8ef4ecd494a160bd36f1b5",
"view_tag": "68"
}
}
}
],
"extra": [ 1, 176, 135, 39, 192, 227, 220, 149, 50, 225, 10, 244, 250, 156, 45, 17, 151, 109, 48, 224, 221, 242, 180, 255, 152, 173, 172, 227, 121, 255, 223, 132, 242
],
"rct_signatures": {
"type": 0
}
}