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: 95fe9980e9276e08fd9801f6f6a4527bd6696a6ab6462a92c1867c035dc83c07
Tx prefix hash: 192f361200938c1cd0b7c34d2e65dc7b31aa25bd44c42041a7b6e6e2a1b42be9
Tx public key: f8e1eef693f45faf2eea03949095a95355beef01a3ae7e20a21727831e814de7
| Timestamp: 1779638949 | Timestamp [UTC]: 2026-05-24 16:09:09 | Age [y:d:h:m:s]: 00:015:10:40:39 |
| Block: 1226 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6673 | RingCT/type: yes/0 |
| Extra: 01f8e1eef693f45faf2eea03949095a95355beef01a3ae7e20a21727831e814de7 | ||
1 output(s) for total of 35.102259617572 HMNY
| stealth address | amount | amount idx | tag |
| 00: 76145db5c8d416174dcb59c660892a52be6dba83383cb6b531323650056083b3 | 35.102259617572 | 1370 of 0 | <b6> |
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": 1286,
"vin": [ {
"gen": {
"height": 1226
}
}
],
"vout": [ {
"amount": 35102259617572,
"target": {
"tagged_key": {
"key": "76145db5c8d416174dcb59c660892a52be6dba83383cb6b531323650056083b3",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 248, 225, 238, 246, 147, 244, 95, 175, 46, 234, 3, 148, 144, 149, 169, 83, 85, 190, 239, 1, 163, 174, 126, 32, 162, 23, 39, 131, 30, 129, 77, 231
],
"rct_signatures": {
"type": 0
}
}