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: 7f46bc4d789c8531101b441349b36930816a06a65f6e84e73d8e5569c8fe838e
Tx prefix hash: 791ef49ed26d9d8c600330a9abe95e84f1e1267ecdb4ab5570f1be1d1db9ad21
Tx public key: 475d8236d75b3f52022168c04915c7fbf80c865a852bb8e7062102c36fcdc220
| Timestamp: 1780087622 | Timestamp [UTC]: 2026-05-29 20:47:02 | Age [y:d:h:m:s]: 00:010:06:51:48 |
| Block: 4825 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3122 | RingCT/type: yes/0 |
| Extra: 01475d8236d75b3f52022168c04915c7fbf80c865a852bb8e7062102c36fcdc22002090000000326697be300 | ||
1 output(s) for total of 34.862123408213 HMNY
| stealth address | amount | amount idx | tag |
| 00: 85dd61f26132d08b3e87a4120506b974e44194b0008fb0c3f4f528faa7a69b7e | 34.862123408213 | 6071 of 0 | <38> |
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": 4885,
"vin": [ {
"gen": {
"height": 4825
}
}
],
"vout": [ {
"amount": 34862123408213,
"target": {
"tagged_key": {
"key": "85dd61f26132d08b3e87a4120506b974e44194b0008fb0c3f4f528faa7a69b7e",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 71, 93, 130, 54, 215, 91, 63, 82, 2, 33, 104, 192, 73, 21, 199, 251, 248, 12, 134, 90, 133, 43, 184, 231, 6, 33, 2, 195, 111, 205, 194, 32, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}