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: 23b058e3682d1a72d202d9fba86dbdbcb70d8be3178be41b86ea2b48bd8f5ace
Tx prefix hash: e3880732465568a8c8dd1a1ab3dbd334fda500ad8e89e98539a5afbf9b6c02ae
Tx public key: 83601b5b2ad79e8911a44cc70e98e46712dbe0b93e458047026a4f1bb0298e36
| Timestamp: 1780815349 | Timestamp [UTC]: 2026-06-07 06:55:49 | Age [y:d:h:m:s]: 00:001:16:23:04 |
| Block: 7057 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 829 | RingCT/type: yes/0 |
| Extra: 0183601b5b2ad79e8911a44cc70e98e46712dbe0b93e458047026a4f1bb0298e36020900000001e49593ff00 | ||
1 output(s) for total of 34.714023629328 HMNY
| stealth address | amount | amount idx | tag |
| 00: 18f30186332d400511f5609ef0976413c718b6891940042f1aee9e387496d543 | 34.714023629328 | 8701 of 0 | <40> |
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": 7117,
"vin": [ {
"gen": {
"height": 7057
}
}
],
"vout": [ {
"amount": 34714023629328,
"target": {
"tagged_key": {
"key": "18f30186332d400511f5609ef0976413c718b6891940042f1aee9e387496d543",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 131, 96, 27, 91, 42, 215, 158, 137, 17, 164, 76, 199, 14, 152, 228, 103, 18, 219, 224, 185, 62, 69, 128, 71, 2, 106, 79, 27, 176, 41, 142, 54, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}