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: 194d07fef6e2be1a0421513d58ac7d1c9b1c7e9e14757c6e61fffebd1ff5a0a0
Tx prefix hash: 0e1b6b2c873490be89e427ec3f4cd8601058aae6bf4f0e754664de368509cfb7
Tx public key: 7dad33129398b744e9a1f645411374b52ae8eb1dce57a4a4ba9a6619f9bfda06
| Timestamp: 1780905351 | Timestamp [UTC]: 2026-06-08 07:55:51 | Age [y:d:h:m:s]: 00:000:13:16:16 |
| Block: 7860 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 26 | RingCT/type: yes/0 |
| Extra: 017dad33129398b744e9a1f645411374b52ae8eb1dce57a4a4ba9a6619f9bfda060209000000024a728a4c00 | ||
1 output(s) for total of 34.660896242381 HMNY
| stealth address | amount | amount idx | tag |
| 00: fb7de32a927a2536489fbe8b5d9b9ca7b71d3653af8c611dbd37f41afc099768 | 34.660896242381 | 9744 of 0 | <ad> |
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": 7920,
"vin": [ {
"gen": {
"height": 7860
}
}
],
"vout": [ {
"amount": 34660896242381,
"target": {
"tagged_key": {
"key": "fb7de32a927a2536489fbe8b5d9b9ca7b71d3653af8c611dbd37f41afc099768",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 125, 173, 51, 18, 147, 152, 183, 68, 233, 161, 246, 69, 65, 19, 116, 181, 42, 232, 235, 29, 206, 87, 164, 164, 186, 154, 102, 25, 249, 191, 218, 6, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}