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: 235b418c2eb5413b2215dd60712bc57dec89497c693d94a3d27eb0c8335a8b05
Tx prefix hash: 6a22d1648e9c88ba2afda8cecd46ca60e3e6ef47efc0efceee242a48b5f153ea
Tx public key: 72089c69467853dd4effed40a01024b53eb249fb87d125cd6e424a72721eb452
| Timestamp: 1779914059 | Timestamp [UTC]: 2026-05-27 20:34:19 | Age [y:d:h:m:s]: 00:012:05:01:38 |
| Block: 3279 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4607 | RingCT/type: yes/0 |
| Extra: 0172089c69467853dd4effed40a01024b53eb249fb87d125cd6e424a72721eb45202090000000326697be300 | ||
1 output(s) for total of 34.965075291452 HMNY
| stealth address | amount | amount idx | tag |
| 00: 35fa503039e5078db83f121db72176733b669c0f68c8b560ba18b3281d789c33 | 34.965075291452 | 3937 of 0 | <0c> |
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": 3339,
"vin": [ {
"gen": {
"height": 3279
}
}
],
"vout": [ {
"amount": 34965075291452,
"target": {
"tagged_key": {
"key": "35fa503039e5078db83f121db72176733b669c0f68c8b560ba18b3281d789c33",
"view_tag": "0c"
}
}
}
],
"extra": [ 1, 114, 8, 156, 105, 70, 120, 83, 221, 78, 255, 237, 64, 160, 16, 36, 181, 62, 178, 73, 251, 135, 209, 37, 205, 110, 66, 74, 114, 114, 30, 180, 82, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}