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: 0e67486e2a602ac9fbaa5b64bcb3e89e9a3c205f83da2060f492b41b9c807592
Tx prefix hash: df4a94340bfdf6f8bbda46d4f5a69bddb2720e1fd8ff8c92313710f8d545c26d
Tx public key: 72043cd56e5cd192b89dc986c52f5d0f1e06999edfb7a6c10066d044dab9738d
| Timestamp: 1779916204 | Timestamp [UTC]: 2026-05-27 21:10:04 | Age [y:d:h:m:s]: 00:012:04:25:53 |
| Block: 3302 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4584 | RingCT/type: yes/0 |
| Extra: 0172043cd56e5cd192b89dc986c52f5d0f1e06999edfb7a6c10066d044dab9738d02090000000226697be300 | ||
1 output(s) for total of 34.968552640097 HMNY
| stealth address | amount | amount idx | tag |
| 00: 576cf9622334ae3df9d4da98987a84e4919a2d1f0843e2180552f8e90b83c057 | 34.968552640097 | 3966 of 0 | <83> |
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": 3362,
"vin": [ {
"gen": {
"height": 3302
}
}
],
"vout": [ {
"amount": 34968552640097,
"target": {
"tagged_key": {
"key": "576cf9622334ae3df9d4da98987a84e4919a2d1f0843e2180552f8e90b83c057",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 114, 4, 60, 213, 110, 92, 209, 146, 184, 157, 201, 134, 197, 47, 93, 15, 30, 6, 153, 158, 223, 183, 166, 193, 0, 102, 208, 68, 218, 185, 115, 141, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}