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: 7932f4264dc05b8fc57001d57076af07d5d12018ddfbaa300f1b48123ed7e120
Tx prefix hash: 1ae1b4ee8b3aedded7269b8301d502050a0b9b2ee2f9a9c8361c8bd20a422c83
Tx public key: 6b87e0293dd75a5374a05a57ef0f735d2bcc2c44d3659354e3d3462ce2b7c32e
| Timestamp: 1779435734 | Timestamp [UTC]: 2026-05-22 07:42:14 | Age [y:d:h:m:s]: 00:017:18:58:22 |
| Block: 127 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7770 | RingCT/type: yes/0 |
| Extra: 016b87e0293dd75a5374a05a57ef0f735d2bcc2c44d3659354e3d3462ce2b7c32e020900000001a662ed0300 | ||
1 output(s) for total of 35.175917380002 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74334ff9e2d3d7a9b1132223ae542b9e9d7e1e29e109ff91756c15ca1ead233d | 35.175917380002 | 123 of 0 | <8d> |
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": 187,
"vin": [ {
"gen": {
"height": 127
}
}
],
"vout": [ {
"amount": 35175917380002,
"target": {
"tagged_key": {
"key": "74334ff9e2d3d7a9b1132223ae542b9e9d7e1e29e109ff91756c15ca1ead233d",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 107, 135, 224, 41, 61, 215, 90, 83, 116, 160, 90, 87, 239, 15, 115, 93, 43, 204, 44, 68, 211, 101, 147, 84, 227, 211, 70, 44, 226, 183, 195, 46, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}