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: 65fc5faf36678dfeb2f290a4ee9fd26db0e3dc56356ae970baadff90fa9bed9f
Tx prefix hash: b65d0487622bff124027ff9d7f4c7da2426b0af656be57c4770ad9944a050d44
Tx public key: bb83ce584ab6661aee94b008bbf3f1f0aa5956c0c4ba06024c4e4925af8efdc3
| Timestamp: 1780984754 | Timestamp [UTC]: 2026-06-09 05:59:14 | Age [y:d:h:m:s]: 00:000:08:49:41 |
| Block: 8122 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 531 | RingCT/type: yes/0 |
| Extra: 01bb83ce584ab6661aee94b008bbf3f1f0aa5956c0c4ba06024c4e4925af8efdc3020900000002e49593ff00 | ||
1 output(s) for total of 34.643579624782 HMNY
| stealth address | amount | amount idx | tag |
| 00: 178363f25412f609ef798cef1027e1cee22678716f8b2b832675aa497e1c4571 | 34.643579624782 | 10058 of 0 | <a0> |
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": 8182,
"vin": [ {
"gen": {
"height": 8122
}
}
],
"vout": [ {
"amount": 34643579624782,
"target": {
"tagged_key": {
"key": "178363f25412f609ef798cef1027e1cee22678716f8b2b832675aa497e1c4571",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 187, 131, 206, 88, 74, 182, 102, 26, 238, 148, 176, 8, 187, 243, 241, 240, 170, 89, 86, 192, 196, 186, 6, 2, 76, 78, 73, 37, 175, 142, 253, 195, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}