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: 8e043b4d5236b7c3e81da1a16d8c50a3cc5c197a85c07babc4c4d25727c79209
Tx prefix hash: b20658b3a3bae8cc391a16d305e4ef6582058cdb704ea8809f97de1ce1235300
Tx public key: dc12b6e3a14939efac99d88f467ae5b8932394e15c51928b62401a1df1ca3f9e
| Timestamp: 1780024322 | Timestamp [UTC]: 2026-05-29 03:12:02 | Age [y:d:h:m:s]: 00:010:23:28:34 |
| Block: 4162 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3735 | RingCT/type: yes/0 |
| Extra: 01dc12b6e3a14939efac99d88f467ae5b8932394e15c51928b62401a1df1ca3f9e02090000000326697be300 | ||
1 output(s) for total of 34.906237006946 HMNY
| stealth address | amount | amount idx | tag |
| 00: 053ac127b12fa7e42bd7b85bb025cbe4eb521d072612846208f206ce867d0149 | 34.906237006946 | 5193 of 0 | <dd> |
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": 4222,
"vin": [ {
"gen": {
"height": 4162
}
}
],
"vout": [ {
"amount": 34906237006946,
"target": {
"tagged_key": {
"key": "053ac127b12fa7e42bd7b85bb025cbe4eb521d072612846208f206ce867d0149",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 220, 18, 182, 227, 161, 73, 57, 239, 172, 153, 216, 143, 70, 122, 229, 184, 147, 35, 148, 225, 92, 81, 146, 139, 98, 64, 26, 29, 241, 202, 63, 158, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}