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: 0c66efb49060c1aff542fc9cf604a0797e03121abe0f73f8e3e51c132e33b0f6
Tx prefix hash: 47f32d3c47abf10227096e3cfe3a6f14b8752a20bd66a101a91531cef0d0a44a
Tx public key: 0c6b1c7c600bdef3150d50021ee881da105fbe90b3488c303ce6f2acdb24fd6b
| Timestamp: 1780687699 | Timestamp [UTC]: 2026-06-05 19:28:19 | Age [y:d:h:m:s]: 00:003:03:50:34 |
| Block: 5494 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2392 | RingCT/type: yes/0 |
| Extra: 010c6b1c7c600bdef3150d50021ee881da105fbe90b3488c303ce6f2acdb24fd6b020900000001e49593ff00 | ||
1 output(s) for total of 34.817667099866 HMNY
| stealth address | amount | amount idx | tag |
| 00: 23d675b65471e03da010f847e4302ad26e3c775772d5a472b924224394b6092f | 34.817667099866 | 6933 of 0 | <ed> |
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": 5554,
"vin": [ {
"gen": {
"height": 5494
}
}
],
"vout": [ {
"amount": 34817667099866,
"target": {
"tagged_key": {
"key": "23d675b65471e03da010f847e4302ad26e3c775772d5a472b924224394b6092f",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 12, 107, 28, 124, 96, 11, 222, 243, 21, 13, 80, 2, 30, 232, 129, 218, 16, 95, 190, 144, 179, 72, 140, 48, 60, 230, 242, 172, 219, 36, 253, 107, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}