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: fa371fa2b6187cd04689efdf7c24a71aeb2c545ffa47feb87c04b37fa32885cc
Tx prefix hash: e4eca64219dd381f9563155de16b5847ca2d17b4d1820c0fda8c7fc484ebf60c
Tx public key: c9c376c7b44ae1a62cad55220d2606db5bb5ebd86e9c6b01a0e035cb870f4d63
| Timestamp: 1779961616 | Timestamp [UTC]: 2026-05-28 09:46:56 | Age [y:d:h:m:s]: 00:016:01:34:09 |
| Block: 3766 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4979 | RingCT/type: yes/0 |
| Extra: 01c9c376c7b44ae1a62cad55220d2606db5bb5ebd86e9c6b01a0e035cb870f4d6302090000000226697be300 | ||
1 output(s) for total of 34.932612023422 HMNY
| stealth address | amount | amount idx | tag |
| 00: 53ffa18a1e39969a106b5d0771d274438817224597d143e7ab466729bebf2891 | 34.932612023422 | 4567 of 0 | <00> |
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": 3826,
"vin": [ {
"gen": {
"height": 3766
}
}
],
"vout": [ {
"amount": 34932612023422,
"target": {
"tagged_key": {
"key": "53ffa18a1e39969a106b5d0771d274438817224597d143e7ab466729bebf2891",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 201, 195, 118, 199, 180, 74, 225, 166, 44, 173, 85, 34, 13, 38, 6, 219, 91, 181, 235, 216, 110, 156, 107, 1, 160, 224, 53, 203, 135, 15, 77, 99, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}