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: f3aaf66461182b79acd98e2a35ea61ab95de75471f27e1bec2b2dba5a93bcf61
Tx prefix hash: a183af93a8c6a4f24c3e6a9e6e9c3c8c5e8f7517ca10aa66464075b285b026a8
Tx public key: 069a3d48159aafa5382d35ef1b8d63d7cdd8b91ab8c2079c9736d97fa68db71d
| Timestamp: 1780800870 | Timestamp [UTC]: 2026-06-07 02:54:30 | Age [y:d:h:m:s]: 00:010:05:10:51 |
| Block: 6833 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1912 | RingCT/type: yes/0 |
| Extra: 01069a3d48159aafa5382d35ef1b8d63d7cdd8b91ab8c2079c9736d97fa68db71d020900000002e49593ff00 | ||
1 output(s) for total of 34.728858243259 HMNY
| stealth address | amount | amount idx | tag |
| 00: af0393b0d79848effe8acf028b342cbd8442bfa17ea6953ac6d31044b0a9f770 | 34.728858243259 | 8437 of 0 | <35> |
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": 6893,
"vin": [ {
"gen": {
"height": 6833
}
}
],
"vout": [ {
"amount": 34728858243259,
"target": {
"tagged_key": {
"key": "af0393b0d79848effe8acf028b342cbd8442bfa17ea6953ac6d31044b0a9f770",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 6, 154, 61, 72, 21, 154, 175, 165, 56, 45, 53, 239, 27, 141, 99, 215, 205, 216, 185, 26, 184, 194, 7, 156, 151, 54, 217, 127, 166, 141, 183, 29, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}