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: ae8128300149343cecb7e441dc4a1925855af2aebe53da63c297ed9e589ebfac
Tx prefix hash: 10a5595da83bbf17a0239a2677bbc82b7156da9c3543fced389d39961741f6ec
Tx public key: e0fba4871eb3ca3dc21c8dbeba9effed75ec7ac9ef8b5571fb6c58a3d7670d7b
| Timestamp: 1779938373 | Timestamp [UTC]: 2026-05-28 03:19:33 | Age [y:d:h:m:s]: 00:011:21:27:14 |
| Block: 3459 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4427 | RingCT/type: yes/0 |
| Extra: 01e0fba4871eb3ca3dc21c8dbeba9effed75ec7ac9ef8b5571fb6c58a3d7670d7b02090000000126697be300 | ||
1 output(s) for total of 34.953073034508 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5510798d6934e8cab7269b88cba39f69bc0527ed0e60509fcb61f326eec6ea5e | 34.953073034508 | 4176 of 0 | <f7> |
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": 3519,
"vin": [ {
"gen": {
"height": 3459
}
}
],
"vout": [ {
"amount": 34953073034508,
"target": {
"tagged_key": {
"key": "5510798d6934e8cab7269b88cba39f69bc0527ed0e60509fcb61f326eec6ea5e",
"view_tag": "f7"
}
}
}
],
"extra": [ 1, 224, 251, 164, 135, 30, 179, 202, 61, 194, 28, 141, 190, 186, 158, 255, 237, 117, 236, 122, 201, 239, 139, 85, 113, 251, 108, 88, 163, 215, 103, 13, 123, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}