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: c658e07a4d3e9fe788b9a561fa824b0ef2f63731b33de0a7a6965f9d2392244c
Tx prefix hash: a43d21119570bd2ed4e521eb96010ae8248d108e50d6bc40aa7a8a6f28eb6893
Tx public key: 31171419c4ec9e68685688c6a60c774f21be75d0d8d2ec74268b4993e00f8948
| Timestamp: 1779466151 | Timestamp [UTC]: 2026-05-22 16:09:11 | Age [y:d:h:m:s]: 00:017:09:26:46 |
| Block: 512 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7374 | RingCT/type: yes/0 |
| Extra: 0131171419c4ec9e68685688c6a60c774f21be75d0d8d2ec74268b4993e00f894802090000000393369e7d00 | ||
1 output(s) for total of 35.150096133085 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7198053e013174b86be01db05f37e502cce0d5ecea7174024981f2289815333c | 35.150096133085 | 516 of 0 | <f5> |
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": 572,
"vin": [ {
"gen": {
"height": 512
}
}
],
"vout": [ {
"amount": 35150096133085,
"target": {
"tagged_key": {
"key": "7198053e013174b86be01db05f37e502cce0d5ecea7174024981f2289815333c",
"view_tag": "f5"
}
}
}
],
"extra": [ 1, 49, 23, 20, 25, 196, 236, 158, 104, 104, 86, 136, 198, 166, 12, 119, 79, 33, 190, 117, 208, 216, 210, 236, 116, 38, 139, 73, 147, 224, 15, 137, 72, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}