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: b78e81191996a8bf5b77355de9f31119877a22fbde97c1863e7545e607be9553
Tx prefix hash: e2590610da14a980243dca0e2a8042c969d445e760dec8a0c7606461f2a698cf
Tx public key: dbc5b27ee6a51b3d303d2722707ae09a6511f605573875a6c23f3e7fe5851cac
| Timestamp: 1779941084 | Timestamp [UTC]: 2026-05-28 04:04:44 | Age [y:d:h:m:s]: 00:011:21:31:13 |
| Block: 3497 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4389 | RingCT/type: yes/0 |
| Extra: 01dbc5b27ee6a51b3d303d2722707ae09a6511f605573875a6c23f3e7fe5851cac02090000000326697be300 | ||
1 output(s) for total of 34.950539751448 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64e3a02431f3e717e88f55fde90ffe429050dade1a2d6358ec06afa86707c876 | 34.950539751448 | 4216 of 0 | <b8> |
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": 3557,
"vin": [ {
"gen": {
"height": 3497
}
}
],
"vout": [ {
"amount": 34950539751448,
"target": {
"tagged_key": {
"key": "64e3a02431f3e717e88f55fde90ffe429050dade1a2d6358ec06afa86707c876",
"view_tag": "b8"
}
}
}
],
"extra": [ 1, 219, 197, 178, 126, 230, 165, 27, 61, 48, 61, 39, 34, 112, 122, 224, 154, 101, 17, 246, 5, 87, 56, 117, 166, 194, 63, 62, 127, 229, 133, 28, 172, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}