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: b49389dca7f0d6561980cb4f04456b2fd48f80ba1312e09b7c9d84d745e0ed9a
Tx prefix hash: db11348e93dd1914d9fa31e2b259112137c6822aeeb373035b38160cf7f5802a
Tx public key: add3a65ca1672c5195b65de15f038039ad48ea35a8adf9c0542380d299c93e9c
| Timestamp: 1780013690 | Timestamp [UTC]: 2026-05-29 00:14:50 | Age [y:d:h:m:s]: 00:011:01:21:07 |
| Block: 4109 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3777 | RingCT/type: yes/0 |
| Extra: 01add3a65ca1672c5195b65de15f038039ad48ea35a8adf9c0542380d299c93e9c02090000000626697be300 | ||
1 output(s) for total of 34.909765841934 HMNY
| stealth address | amount | amount idx | tag |
| 00: 743b71e3d92d9e9ab9baca064bf70e136dff29c8aa549ccc155e5bea75551389 | 34.909765841934 | 5120 of 0 | <7f> |
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": 4169,
"vin": [ {
"gen": {
"height": 4109
}
}
],
"vout": [ {
"amount": 34909765841934,
"target": {
"tagged_key": {
"key": "743b71e3d92d9e9ab9baca064bf70e136dff29c8aa549ccc155e5bea75551389",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 173, 211, 166, 92, 161, 103, 44, 81, 149, 182, 93, 225, 95, 3, 128, 57, 173, 72, 234, 53, 168, 173, 249, 192, 84, 35, 128, 210, 153, 201, 62, 156, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}