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: 5ba9cedfc2f5cd1e974394171a2dce0c7615ce5f8dbc4a1fd7b7727a1a8191e8
Tx prefix hash: 03219a14bf9ce344839743e78504ccec0185943ac62f3b64e6d3343382480072
Tx public key: a49cff0a73f166cbf0ca2bc77a6f070a39e723aa87cb0c551319bf4fdd72217b
| Timestamp: 1779960454 | Timestamp [UTC]: 2026-05-28 09:27:34 | Age [y:d:h:m:s]: 00:019:23:47:32 |
| Block: 3749 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4996 | RingCT/type: yes/0 |
| Extra: 01a49cff0a73f166cbf0ca2bc77a6f070a39e723aa87cb0c551319bf4fdd72217b02090000000226697be300 | ||
1 output(s) for total of 34.933744730252 HMNY
| stealth address | amount | amount idx | tag |
| 00: 595dcb4d7153e05d9cb0f0cc8ae5b02e5888ca6168c5250b53981c56056cd2e2 | 34.933744730252 | 4544 of 0 | <a9> |
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": 3809,
"vin": [ {
"gen": {
"height": 3749
}
}
],
"vout": [ {
"amount": 34933744730252,
"target": {
"tagged_key": {
"key": "595dcb4d7153e05d9cb0f0cc8ae5b02e5888ca6168c5250b53981c56056cd2e2",
"view_tag": "a9"
}
}
}
],
"extra": [ 1, 164, 156, 255, 10, 115, 241, 102, 203, 240, 202, 43, 199, 122, 111, 7, 10, 57, 231, 35, 170, 135, 203, 12, 85, 19, 25, 191, 79, 221, 114, 33, 123, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}