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: 8151296e14bfa18aef0557df869a115f121290343d8ea7f1e76cf3a33b0a99ed
Tx prefix hash: 8bdf1512d6d24d3e3230f238199a13fe7a00188e310ce73e28be44fd876f281b
Tx public key: f2352a7a8970e9e514454d5b9c9a3332172cd32df91b927eb2eba30ef1e5b2fe
| Timestamp: 1780895238 | Timestamp [UTC]: 2026-06-08 05:07:18 | Age [y:d:h:m:s]: 00:000:16:04:49 |
| Block: 7757 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 129 | RingCT/type: yes/0 |
| Extra: 01f2352a7a8970e9e514454d5b9c9a3332172cd32df91b927eb2eba30ef1e5b2fe0209000000014a728a4c00 | ||
1 output(s) for total of 34.667706290340 HMNY
| stealth address | amount | amount idx | tag |
| 00: 769325f5783935be2844f6c48ac8bfc839524269bd188c6f878ccf6a1b848e97 | 34.667706290340 | 9607 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": 7817,
"vin": [ {
"gen": {
"height": 7757
}
}
],
"vout": [ {
"amount": 34667706290340,
"target": {
"tagged_key": {
"key": "769325f5783935be2844f6c48ac8bfc839524269bd188c6f878ccf6a1b848e97",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 242, 53, 42, 122, 137, 112, 233, 229, 20, 69, 77, 91, 156, 154, 51, 50, 23, 44, 211, 45, 249, 27, 146, 126, 178, 235, 163, 14, 241, 229, 178, 254, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}