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: 8f80e9093a14190b028e994976561fb3a72d75f0ec033d0914b5829d8dc0c0c1
Tx prefix hash: 7ff2a042f797ae88e25f7b1da4f807af6400c39d8163de2348e7ff9604c8026b
Tx public key: b25cfe583b992b1b10cd8af212250f5807ded619dbbbf03f416d91a1489d6949
| Timestamp: 1779716041 | Timestamp [UTC]: 2026-05-25 13:34:01 | Age [y:d:h:m:s]: 00:014:12:01:56 |
| Block: 1645 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6241 | RingCT/type: yes/0 |
| Extra: 01b25cfe583b992b1b10cd8af212250f5807ded619dbbbf03f416d91a1489d6949020900000001ba6d17be00 | ||
1 output(s) for total of 35.074217806090 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9fb3ef7454c357e9ce440566b64a540486b0fe28359d217d52b6a1116aa658f | 35.074217806090 | 1807 of 0 | <24> |
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": 1705,
"vin": [ {
"gen": {
"height": 1645
}
}
],
"vout": [ {
"amount": 35074217806090,
"target": {
"tagged_key": {
"key": "d9fb3ef7454c357e9ce440566b64a540486b0fe28359d217d52b6a1116aa658f",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 178, 92, 254, 88, 59, 153, 43, 27, 16, 205, 138, 242, 18, 37, 15, 88, 7, 222, 214, 25, 219, 187, 240, 63, 65, 109, 145, 161, 72, 157, 105, 73, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}