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: 3fc25501dec826ee26855f8da785f38e334b7059fc3ebda5b901eb63cc3f6d4c
Tx prefix hash: bf1bd542e587ccbbfb99ed0483d1ab22a910557a1bdddee6fa8ec42685697346
Tx public key: a7f18ff2fbdfd17401b5e9caaf21b63f6ddd146527bf1cb99d6a17ec2c78ca66
| Timestamp: 1779768333 | Timestamp [UTC]: 2026-05-26 04:05:33 | Age [y:d:h:m:s]: 00:020:04:14:02 |
| Block: 1987 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6758 | RingCT/type: yes/0 |
| Extra: 01a7f18ff2fbdfd17401b5e9caaf21b63f6ddd146527bf1cb99d6a17ec2c78ca6602090000000126697be300 | ||
1 output(s) for total of 35.051345868530 HMNY
| stealth address | amount | amount idx | tag |
| 00: 849ef5eec4681933df33da99701440974b88d11e09de5d04d9d3b4bbbe1661a4 | 35.051345868530 | 2263 of 0 | <b5> |
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": 2047,
"vin": [ {
"gen": {
"height": 1987
}
}
],
"vout": [ {
"amount": 35051345868530,
"target": {
"tagged_key": {
"key": "849ef5eec4681933df33da99701440974b88d11e09de5d04d9d3b4bbbe1661a4",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 167, 241, 143, 242, 251, 223, 209, 116, 1, 181, 233, 202, 175, 33, 182, 63, 109, 221, 20, 101, 39, 191, 28, 185, 157, 106, 23, 236, 44, 120, 202, 102, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}