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: bebb5642151a4223f6bad045e4b6d0d0a1aca05c939d9024d4bbec8c2b142ef5
Tx prefix hash: ffe2eea6f1e5a69817076a031108becda3002245864526380e4c1662064849fa
Tx public key: c577847e7db95f326df3efe35603ee93a54fa28b78cc5623f3ec56e43a0bb159
| Timestamp: 1779641961 | Timestamp [UTC]: 2026-05-24 16:59:21 | Age [y:d:h:m:s]: 00:015:10:51:37 |
| Block: 1371 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6579 | RingCT/type: yes/0 |
| Extra: 01c577847e7db95f326df3efe35603ee93a54fa28b78cc5623f3ec56e43a0bb159020900000001ba6d17be00 | ||
1 output(s) for total of 35.092552874853 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9ecc593830fb239bedc90f623c217de7f067b3358d2f6cc4275e12873818927c | 35.092552874853 | 1521 of 0 | <65> |
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": 1431,
"vin": [ {
"gen": {
"height": 1371
}
}
],
"vout": [ {
"amount": 35092552874853,
"target": {
"tagged_key": {
"key": "9ecc593830fb239bedc90f623c217de7f067b3358d2f6cc4275e12873818927c",
"view_tag": "65"
}
}
}
],
"extra": [ 1, 197, 119, 132, 126, 125, 185, 95, 50, 109, 243, 239, 227, 86, 3, 238, 147, 165, 79, 162, 139, 120, 204, 86, 35, 243, 236, 86, 228, 58, 11, 177, 89, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}