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: c8569ad14c05c857635714d19ddd2eb472a0fd1dd6a93c49f8df05b34eae1f88
Tx prefix hash: a227c4062f17dc747d4d516bae9b313ace04b0922b1d14306d2635c659155a57
Tx public key: a8a73bafd9251a1a5fb6a8a475ae6691033578fc726c2732847d2bc8ab46dd63
| Timestamp: 1779544516 | Timestamp [UTC]: 2026-05-23 13:55:16 | Age [y:d:h:m:s]: 00:016:13:43:34 |
| Block: 690 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7252 | RingCT/type: yes/0 |
| Extra: 01a8a73bafd9251a1a5fb6a8a475ae6691033578fc726c2732847d2bc8ab46dd6302090000000eba6d17be00 | ||
1 output(s) for total of 35.138164406450 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7d0730fecc40d60376c03beb56ac53968cf54f0e93696a1e6543483a9ce50eb4 | 35.138164406450 | 781 of 0 | <1c> |
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": 750,
"vin": [ {
"gen": {
"height": 690
}
}
],
"vout": [ {
"amount": 35138164406450,
"target": {
"tagged_key": {
"key": "7d0730fecc40d60376c03beb56ac53968cf54f0e93696a1e6543483a9ce50eb4",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 168, 167, 59, 175, 217, 37, 26, 26, 95, 182, 168, 164, 117, 174, 102, 145, 3, 53, 120, 252, 114, 108, 39, 50, 132, 125, 43, 200, 171, 70, 221, 99, 2, 9, 0, 0, 0, 14, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}