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: 317e0adbe90b0b3ce269b3faccc812f4fc2f3bac119b0cbc4873d421e16330e0
Tx prefix hash: 16bafc94c487e3d4fcd0e3ebcf9d354d911a5600b683abdcbf712ea8f89dc15d
Tx public key: e7b44e733fcf75eabf66c8434b03b4c4fe6a079b476bf8f333654d175a280c9c
| Timestamp: 1779721089 | Timestamp [UTC]: 2026-05-25 14:58:09 | Age [y:d:h:m:s]: 00:014:10:37:48 |
| Block: 1755 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6131 | RingCT/type: yes/0 |
| Extra: 01e7b44e733fcf75eabf66c8434b03b4c4fe6a079b476bf8f333654d175a280c9c020900000001ba6d17be00 | ||
1 output(s) for total of 35.066859707243 HMNY
| stealth address | amount | amount idx | tag |
| 00: 746f757b92c9bb8462aa094baf0ca5aab55dfa2b866c8481854a02df0a20db21 | 35.066859707243 | 1935 of 0 | <a5> |
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": 1815,
"vin": [ {
"gen": {
"height": 1755
}
}
],
"vout": [ {
"amount": 35066859707243,
"target": {
"tagged_key": {
"key": "746f757b92c9bb8462aa094baf0ca5aab55dfa2b866c8481854a02df0a20db21",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 231, 180, 78, 115, 63, 207, 117, 234, 191, 102, 200, 67, 75, 3, 180, 196, 254, 106, 7, 155, 71, 107, 248, 243, 51, 101, 77, 23, 90, 40, 12, 156, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}