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: d2646319933d5fced518ddcf9be39dc0253c37d1a9dd7dee3e2584732ec28289
Tx prefix hash: 8c99a7017e3f64586cb4f2ceff20ade3e05dd26caf9be69fb6319fdbc7853099
Tx public key: 39348aedba624c411c30904fdb9f5a10759f596e7a8438adcb7ea45b179b2770
| Timestamp: 1780993662 | Timestamp [UTC]: 2026-06-09 08:27:42 | Age [y:d:h:m:s]: 00:000:06:21:13 |
| Block: 8280 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 375 | RingCT/type: yes/0 |
| Extra: 0139348aedba624c411c30904fdb9f5a10759f596e7a8438adcb7ea45b179b2770020900000003e49593ff00 | ||
1 output(s) for total of 34.633140961101 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7863a2870749bf67366e0bb96cdc5ac6a6abfbace79e5f89d3b0c74606852c23 | 34.633140961101 | 10246 of 0 | <67> |
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": 8340,
"vin": [ {
"gen": {
"height": 8280
}
}
],
"vout": [ {
"amount": 34633140961101,
"target": {
"tagged_key": {
"key": "7863a2870749bf67366e0bb96cdc5ac6a6abfbace79e5f89d3b0c74606852c23",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 57, 52, 138, 237, 186, 98, 76, 65, 28, 48, 144, 79, 219, 159, 90, 16, 117, 159, 89, 110, 122, 132, 56, 173, 203, 126, 164, 91, 23, 155, 39, 112, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}