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: 94bf011241bc50dd6b2ca459c5eadbfe04d059f5646abb17cef464b89d1c352e
Tx prefix hash: 603cac4f5fabc334a850c9fc679e6ad9ceee3ed5e0ab75a920b68e7f72a19e3f
Tx public key: 33cc3bbe73045e9f2287163a605390b50b0701095d503aabfbc61713f49823ce
| Timestamp: 1779718525 | Timestamp [UTC]: 2026-05-25 14:15:25 | Age [y:d:h:m:s]: 00:018:20:46:51 |
| Block: 1705 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7040 | RingCT/type: yes/0 |
| Extra: 0133cc3bbe73045e9f2287163a605390b50b0701095d503aabfbc61713f49823ce020900000001ba6d17be00 | ||
1 output(s) for total of 35.070204106249 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9f38d5476d1bfb5582c45356c5ccc3b4e97433f48ad5be1c5a29a20dafd2c9ad | 35.070204106249 | 1876 of 0 | <c0> |
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": 1765,
"vin": [ {
"gen": {
"height": 1705
}
}
],
"vout": [ {
"amount": 35070204106249,
"target": {
"tagged_key": {
"key": "9f38d5476d1bfb5582c45356c5ccc3b4e97433f48ad5be1c5a29a20dafd2c9ad",
"view_tag": "c0"
}
}
}
],
"extra": [ 1, 51, 204, 59, 190, 115, 4, 94, 159, 34, 135, 22, 58, 96, 83, 144, 181, 11, 7, 1, 9, 93, 80, 58, 171, 251, 198, 23, 19, 244, 152, 35, 206, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}