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: 5879c80bf1a213043eb07123d14818434856c720132aee22fb0ac9111cafe695
Tx prefix hash: 1ed31ff241dceb128eba93aa7b695294734bd31e69c8990de936489d0bf5e8fa
Tx public key: e1282a25ad2438594ee73dbd28a1cfd793cd094f80d3faaff93bd48055c95d50
| Timestamp: 1779725331 | Timestamp [UTC]: 2026-05-25 16:08:51 | Age [y:d:h:m:s]: 00:014:07:10:02 |
| Block: 1852 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6034 | RingCT/type: yes/0 |
| Extra: 01e1282a25ad2438594ee73dbd28a1cfd793cd094f80d3faaff93bd48055c95d50020900000003ba6d17be00 | ||
1 output(s) for total of 35.060372482673 HMNY
| stealth address | amount | amount idx | tag |
| 00: 67b0495d8bb462db09d90bdbc1a73f0e5608ba82e999aca3e10c322cd73c72b8 | 35.060372482673 | 2048 of 0 | <8f> |
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": 1912,
"vin": [ {
"gen": {
"height": 1852
}
}
],
"vout": [ {
"amount": 35060372482673,
"target": {
"tagged_key": {
"key": "67b0495d8bb462db09d90bdbc1a73f0e5608ba82e999aca3e10c322cd73c72b8",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 225, 40, 42, 37, 173, 36, 56, 89, 78, 231, 61, 189, 40, 161, 207, 215, 147, 205, 9, 79, 128, 211, 250, 175, 249, 59, 212, 128, 85, 201, 93, 80, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}