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: 0af6e7160a72be2333f8d33a23f47a9f3019599a03032326403b49a4d38a2ce8
Tx prefix hash: d08409d77a2496381948cb769a2a13e9f6775217fd2289e689036b3b247b5dfb
Tx public key: 53b1dfe043d6dc3007a55e0311e89d0d5c1fd3b507caa694dbc3e9e1adcf43f9
| Timestamp: 1779431284 | Timestamp [UTC]: 2026-05-22 06:28:04 | Age [y:d:h:m:s]: 00:017:14:44:03 |
| Block: 12 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0791 kB |
| Tx version: 2 | No of confirmations: 7874 | RingCT/type: yes/0 |
| Extra: 0153b1dfe043d6dc3007a55e0311e89d0d5c1fd3b507caa694dbc3e9e1adcf43f9 | ||
1 output(s) for total of 35.183633898481 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0c2c6123176257d3c0ce37eb25cb5b38d80168e9d870f4cfde819030a85cf258 | 35.183633898481 | 8 of 0 | - |
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": 72,
"vin": [ {
"gen": {
"height": 12
}
}
],
"vout": [ {
"amount": 35183633898481,
"target": {
"key": "0c2c6123176257d3c0ce37eb25cb5b38d80168e9d870f4cfde819030a85cf258"
}
}
],
"extra": [ 1, 83, 177, 223, 224, 67, 214, 220, 48, 7, 165, 94, 3, 17, 232, 157, 13, 92, 31, 211, 181, 7, 202, 166, 148, 219, 195, 233, 225, 173, 207, 67, 249
],
"rct_signatures": {
"type": 0
}
}