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: a1c22855b1ea5d411a5053075e34e662e1b9c6b34cedf3448218ef34efa1aff6
Tx prefix hash: 5c6d036dfb3b140ac3e84391c156b03ebf0dedcd82f1a49c63252b5a98190235
Tx public key: 546925c7f6b751e19080d8b22b02c18363fdeee1c6c900beb6cd54938b976590
| Timestamp: 1779640198 | Timestamp [UTC]: 2026-05-24 16:29:58 | Age [y:d:h:m:s]: 00:015:09:05:59 |
| Block: 1282 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6604 | RingCT/type: yes/0 |
| Extra: 01546925c7f6b751e19080d8b22b02c18363fdeee1c6c900beb6cd54938b976590 | ||
1 output(s) for total of 35.098510488400 HMNY
| stealth address | amount | amount idx | tag |
| 00: f1a26dac615c81eef3d75f2b3480785cfab0ef84b5a9343021fb5f2f77cb5644 | 35.098510488400 | 1430 of 0 | <ea> |
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": 1342,
"vin": [ {
"gen": {
"height": 1282
}
}
],
"vout": [ {
"amount": 35098510488400,
"target": {
"tagged_key": {
"key": "f1a26dac615c81eef3d75f2b3480785cfab0ef84b5a9343021fb5f2f77cb5644",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 84, 105, 37, 199, 246, 183, 81, 225, 144, 128, 216, 178, 43, 2, 193, 131, 99, 253, 238, 225, 198, 201, 0, 190, 182, 205, 84, 147, 139, 151, 101, 144
],
"rct_signatures": {
"type": 0
}
}