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: 91da1066fb748c4d6f2b08eeadeb18157b355edf2d580f89abc022a4089caf4b
Tx prefix hash: b91242c53669ae0fcdece258a6c6fc6b5dfa624ea5eb3faeba88b018b404a725
Tx public key: c4d2280539d01019c81d2fda7743f890a821e0750563da8083d0ff1759add9fd
| Timestamp: 1779726223 | Timestamp [UTC]: 2026-05-25 16:23:43 | Age [y:d:h:m:s]: 00:014:12:09:19 |
| Block: 1859 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6167 | RingCT/type: yes/0 |
| Extra: 01c4d2280539d01019c81d2fda7743f890a821e0750563da8083d0ff1759add9fd020900000002ba6d17be00 | ||
1 output(s) for total of 35.059904378877 HMNY
| stealth address | amount | amount idx | tag |
| 00: 104b6647765c9d79de0c414b3d504d1061549b00d5583fb7a07e5b7763fe447f | 35.059904378877 | 2060 of 0 | <19> |
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": 1919,
"vin": [ {
"gen": {
"height": 1859
}
}
],
"vout": [ {
"amount": 35059904378877,
"target": {
"tagged_key": {
"key": "104b6647765c9d79de0c414b3d504d1061549b00d5583fb7a07e5b7763fe447f",
"view_tag": "19"
}
}
}
],
"extra": [ 1, 196, 210, 40, 5, 57, 208, 16, 25, 200, 29, 47, 218, 119, 67, 248, 144, 168, 33, 224, 117, 5, 99, 218, 128, 131, 208, 255, 23, 89, 173, 217, 253, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}