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: d85411bd0af2be7ee6e07b0602fc44ef025ddd1d18b7e5113b7adad66c54032b
Tx prefix hash: 26006a3b73f930e0b918d8c0c5c9eec294494a405155086e7b2762fc6ecb7d5f
Tx public key: 130d8197b42b1b89fe4f286adebabbf1ec54fcf70df1b436733538c3239ebbec
| Timestamp: 1779719754 | Timestamp [UTC]: 2026-05-25 14:35:54 | Age [y:d:h:m:s]: 00:022:18:00:20 |
| Block: 1732 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7013 | RingCT/type: yes/0 |
| Extra: 01130d8197b42b1b89fe4f286adebabbf1ec54fcf70df1b436733538c3239ebbec020900000001ba6d17be00 | ||
1 output(s) for total of 35.068398091173 HMNY
| stealth address | amount | amount idx | tag |
| 00: b86563ee2f55212339b97ad16a6ade51d56d7f3a5b543eff0eea8a153911d726 | 35.068398091173 | 1908 of 0 | <69> |
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": 1792,
"vin": [ {
"gen": {
"height": 1732
}
}
],
"vout": [ {
"amount": 35068398091173,
"target": {
"tagged_key": {
"key": "b86563ee2f55212339b97ad16a6ade51d56d7f3a5b543eff0eea8a153911d726",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 19, 13, 129, 151, 180, 43, 27, 137, 254, 79, 40, 106, 222, 186, 187, 241, 236, 84, 252, 247, 13, 241, 180, 54, 115, 53, 56, 195, 35, 158, 187, 236, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}