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: 1f5ced8bdfd026bad33b672048f273b53cb2ce7a63bc4a252bddee34da1e49df
Tx prefix hash: fbba27ad0523ba52b85316a4b9af31a35a90e88ff1ea2740152608ba8109007a
Tx public key: bdd958d74d0f3860b4809dd44b16033e46afc8c9d9a91494bad80b6f1e480a75
| Timestamp: 1779631071 | Timestamp [UTC]: 2026-05-24 13:57:51 | Age [y:d:h:m:s]: 00:015:13:40:59 |
| Block: 895 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 7044 | RingCT/type: yes/0 |
| Extra: 01bdd958d74d0f3860b4809dd44b16033e46afc8c9d9a91494bad80b6f1e480a75 | ||
1 output(s) for total of 35.124427829453 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32fb52bf6ce30ae409c90d0f19ccdfba782a5d07174f9bda01f141ca82f1f939 | 35.124427829453 | 1027 of 0 | <e4> |
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": 955,
"vin": [ {
"gen": {
"height": 895
}
}
],
"vout": [ {
"amount": 35124427829453,
"target": {
"tagged_key": {
"key": "32fb52bf6ce30ae409c90d0f19ccdfba782a5d07174f9bda01f141ca82f1f939",
"view_tag": "e4"
}
}
}
],
"extra": [ 1, 189, 217, 88, 215, 77, 15, 56, 96, 180, 128, 157, 212, 75, 22, 3, 62, 70, 175, 200, 201, 217, 169, 20, 148, 186, 216, 11, 111, 30, 72, 10, 117
],
"rct_signatures": {
"type": 0
}
}