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: bddfc38323299a528fec4604e4a8c3002e90ef1140286afd05d1c46bc5c506f8
Tx prefix hash: da11252455870b5423166884050315bf35c7dcd9d3eb1e0a02960ecd16fa8064
Tx public key: 65c49ce7ff293dda02c3287aefd32a4fabf762323ec1e6afa4c18095f3f4c372
| Timestamp: 1779630122 | Timestamp [UTC]: 2026-05-24 13:42:02 | Age [y:d:h:m:s]: 00:015:11:53:55 |
| Block: 859 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7027 | RingCT/type: yes/0 |
| Extra: 0165c49ce7ff293dda02c3287aefd32a4fabf762323ec1e6afa4c18095f3f4c372020900000001ba6d17be00 | ||
1 output(s) for total of 35.126839717616 HMNY
| stealth address | amount | amount idx | tag |
| 00: 12e5c9d7334edb9478c184ae23d2a137a82dee16652a2fc71067f30625ab8177 | 35.126839717616 | 991 of 0 | <36> |
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": 919,
"vin": [ {
"gen": {
"height": 859
}
}
],
"vout": [ {
"amount": 35126839717616,
"target": {
"tagged_key": {
"key": "12e5c9d7334edb9478c184ae23d2a137a82dee16652a2fc71067f30625ab8177",
"view_tag": "36"
}
}
}
],
"extra": [ 1, 101, 196, 156, 231, 255, 41, 61, 218, 2, 195, 40, 122, 239, 211, 42, 79, 171, 247, 98, 50, 62, 193, 230, 175, 164, 193, 128, 149, 243, 244, 195, 114, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}