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: 2b65b1dba14c5df95e21790e9ddaed9a17693523b1b04ffd03ca097c8d019803
Tx prefix hash: 8a4434a1facc4912c2f197a56650942c416cd3d98cb57a098567abeafb7a315f
Tx public key: a16da53751a509130f32c49df783e0c76355c9cc6078ba6f69d2f44e59e22049
| Timestamp: 1780990473 | Timestamp [UTC]: 2026-06-09 07:34:33 | Age [y:d:h:m:s]: 00:000:08:25:11 |
| Block: 8221 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 470 | RingCT/type: yes/0 |
| Extra: 01a16da53751a509130f32c49df783e0c76355c9cc6078ba6f69d2f44e59e22049020900000001e49593ff00 | ||
1 output(s) for total of 34.637038575089 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0fa52bb813728867fefe569f472af96a9469330a69c7b3220ee97c643db6e986 | 34.637038575089 | 10177 of 0 | <f1> |
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": 8281,
"vin": [ {
"gen": {
"height": 8221
}
}
],
"vout": [ {
"amount": 34637038575089,
"target": {
"tagged_key": {
"key": "0fa52bb813728867fefe569f472af96a9469330a69c7b3220ee97c643db6e986",
"view_tag": "f1"
}
}
}
],
"extra": [ 1, 161, 109, 165, 55, 81, 165, 9, 19, 15, 50, 196, 157, 247, 131, 224, 199, 99, 85, 201, 204, 96, 120, 186, 111, 105, 210, 244, 78, 89, 226, 32, 73, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}