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: c891b8a5a722da4d55ce9d4b871eb407f3f74c57d14f5960725e8a36883924b8
Tx prefix hash: 253fab815cd2fe6d94b4a03ba241e38e3ee6a5d4c16d7af5cfeee23203b224eb
Tx public key: c24ac8b0934845dd2478484c75980f3f5b60d62c3228d6d1929af4e389a7f6a4
| Timestamp: 1779717581 | Timestamp [UTC]: 2026-05-25 13:59:41 | Age [y:d:h:m:s]: 00:014:09:19:12 |
| Block: 1686 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6200 | RingCT/type: yes/0 |
| Extra: 01c24ac8b0934845dd2478484c75980f3f5b60d62c3228d6d1929af4e389a7f6a4020900000001ba6d17be00 | ||
1 output(s) for total of 35.078064261502 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3089f17a79d9c99b79f9b5021cca8129fbba280548c46c95494ebac3083a1b02 | 35.078064261502 | 1853 of 0 | <a7> |
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": 1746,
"vin": [ {
"gen": {
"height": 1686
}
}
],
"vout": [ {
"amount": 35078064261502,
"target": {
"tagged_key": {
"key": "3089f17a79d9c99b79f9b5021cca8129fbba280548c46c95494ebac3083a1b02",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 194, 74, 200, 176, 147, 72, 69, 221, 36, 120, 72, 76, 117, 152, 15, 63, 91, 96, 214, 44, 50, 40, 214, 209, 146, 154, 244, 227, 137, 167, 246, 164, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}