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: 8a44aa53f476a934b5fed131fcea5cf6ec78fa278e5002d9ef169b1bd5b3577c
Tx prefix hash: a7d035caec784adfdda122dfa6182eb2012421a851a8a04ccb058eb7441d00c3
Tx public key: a53e691fd78326b4f202d0ad3d55b89a381da80fa97b624cc8734adf3f0a2182
| Timestamp: 1780772976 | Timestamp [UTC]: 2026-06-06 19:09:36 | Age [y:d:h:m:s]: 00:002:21:59:27 |
| Block: 6680 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2054 | RingCT/type: yes/0 |
| Extra: 01a53e691fd78326b4f202d0ad3d55b89a381da80fa97b624cc8734adf3f0a2182020900000001e49593ff00 | ||
1 output(s) for total of 34.744806058015 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f215a10b55453bacf8cd7cce5532554a43b2b81085ac8d174c16eadd6ba60e1 | 34.744806058015 | 8238 of 0 | <4a> |
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": 6740,
"vin": [ {
"gen": {
"height": 6680
}
}
],
"vout": [ {
"amount": 34744806058015,
"target": {
"tagged_key": {
"key": "8f215a10b55453bacf8cd7cce5532554a43b2b81085ac8d174c16eadd6ba60e1",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 165, 62, 105, 31, 215, 131, 38, 180, 242, 2, 208, 173, 61, 85, 184, 154, 56, 29, 168, 15, 169, 123, 98, 76, 200, 115, 74, 223, 63, 10, 33, 130, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}