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: e1f6a02ae82d42767e04608eef42a28f7e7e9384befcdd1acc915ccf82e0954a
Tx prefix hash: de3626d196475fbe0a9bf5aed51f443f2f06cc60015c9acafc36d7b3e10bf362
Tx public key: d64be2aa5426dc44f10774a01c706048ba6a83d23579ab6ed3ed24cd9b679e9d
| Timestamp: 1779641152 | Timestamp [UTC]: 2026-05-24 16:45:52 | Age [y:d:h:m:s]: 00:015:09:54:44 |
| Block: 1327 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6569 | RingCT/type: yes/0 |
| Extra: 01d64be2aa5426dc44f10774a01c706048ba6a83d23579ab6ed3ed24cd9b679e9d020900000001ba6d17be00 | ||
1 output(s) for total of 35.095498085487 HMNY
| stealth address | amount | amount idx | tag |
| 00: 473b55ec05f48243c4f2e74d3d60a6c6ebb5ff6339975ba6d5084f7cf293e10b | 35.095498085487 | 1475 of 0 | <58> |
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": 1387,
"vin": [ {
"gen": {
"height": 1327
}
}
],
"vout": [ {
"amount": 35095498085487,
"target": {
"tagged_key": {
"key": "473b55ec05f48243c4f2e74d3d60a6c6ebb5ff6339975ba6d5084f7cf293e10b",
"view_tag": "58"
}
}
}
],
"extra": [ 1, 214, 75, 226, 170, 84, 38, 220, 68, 241, 7, 116, 160, 28, 112, 96, 72, 186, 106, 131, 210, 53, 121, 171, 110, 211, 237, 36, 205, 155, 103, 158, 157, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}