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: 0def383e6f6a9a647baa116ca559e9dbc31fd16de6d84485e73703ec12b83a49
Tx prefix hash: 73b903a2847597c1eda9232c19d5410731f2a9252d55b5da83f80267cd68af4b
Tx public key: b44aa0eff523cf553b8fe2a61e870933ce352a5d8e817232f26b4636e531d555
| Timestamp: 1779462258 | Timestamp [UTC]: 2026-05-22 15:04:18 | Age [y:d:h:m:s]: 00:017:10:31:39 |
| Block: 461 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7425 | RingCT/type: yes/0 |
| Extra: 01b44aa0eff523cf553b8fe2a61e870933ce352a5d8e817232f26b4636e531d55502090000000393369e7d00 | ||
1 output(s) for total of 35.153515520531 HMNY
| stealth address | amount | amount idx | tag |
| 00: 73c996802f02e7dff95e66ba4065337c385ea1a141c49786669252ee0813d329 | 35.153515520531 | 465 of 0 | <85> |
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": 521,
"vin": [ {
"gen": {
"height": 461
}
}
],
"vout": [ {
"amount": 35153515520531,
"target": {
"tagged_key": {
"key": "73c996802f02e7dff95e66ba4065337c385ea1a141c49786669252ee0813d329",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 180, 74, 160, 239, 245, 35, 207, 85, 59, 143, 226, 166, 30, 135, 9, 51, 206, 53, 42, 93, 142, 129, 114, 50, 242, 107, 70, 54, 229, 49, 213, 85, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}