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: 538f6617a4bfebd19c3d160df23a838b62b1d7d2f177c5ad6312af4278d81d92
Tx prefix hash: 3ee39d0f5b6e19ba9cea55dc6c1d0d9d15e643c94cf53ca651cb70a3b7b920d8
Tx public key: 949d0113ba921a048cc33677220caf4700dabc80021341b0ae12b7dfd0c44d24
| Timestamp: 1779640946 | Timestamp [UTC]: 2026-05-24 16:42:26 | Age [y:d:h:m:s]: 00:015:10:07:22 |
| Block: 1314 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6593 | RingCT/type: yes/0 |
| Extra: 01949d0113ba921a048cc33677220caf4700dabc80021341b0ae12b7dfd0c44d24020900000001ba6d17be00 | ||
1 output(s) for total of 35.096368308660 HMNY
| stealth address | amount | amount idx | tag |
| 00: e56d5b2f796f24edad772050c0510565477cf87e5dfe2ea68b7ca889790cdf1e | 35.096368308660 | 1462 of 0 | <37> |
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": 1374,
"vin": [ {
"gen": {
"height": 1314
}
}
],
"vout": [ {
"amount": 35096368308660,
"target": {
"tagged_key": {
"key": "e56d5b2f796f24edad772050c0510565477cf87e5dfe2ea68b7ca889790cdf1e",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 148, 157, 1, 19, 186, 146, 26, 4, 140, 195, 54, 119, 34, 12, 175, 71, 0, 218, 188, 128, 2, 19, 65, 176, 174, 18, 183, 223, 208, 196, 77, 36, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}