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: 80f0a507424d0a616b6f44e98e5da2aecec0c992506d9c61b5dd2916e8d51efe
Tx prefix hash: c4dd945c53b9c4ae029735d8cd86b03147da698c426c50ef0c27a98b7e39f2f9
Tx public key: e01f1cf205cb1d84f7751344a173a84312357bb7dca6022124a720214ff71afd
| Timestamp: 1780756280 | Timestamp [UTC]: 2026-06-06 14:31:20 | Age [y:d:h:m:s]: 00:002:10:15:27 |
| Block: 6534 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1352 | RingCT/type: yes/0 |
| Extra: 01e01f1cf205cb1d84f7751344a173a84312357bb7dca6022124a720214ff71afd020900000003e49593ff00 | ||
1 output(s) for total of 34.752890082867 HMNY
| stealth address | amount | amount idx | tag |
| 00: 379469d46c746944339dec913ab6cceee1307bdf6aebde70c27c81caf9f10a85 | 34.752890082867 | 8038 of 0 | <b0> |
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": 6594,
"vin": [ {
"gen": {
"height": 6534
}
}
],
"vout": [ {
"amount": 34752890082867,
"target": {
"tagged_key": {
"key": "379469d46c746944339dec913ab6cceee1307bdf6aebde70c27c81caf9f10a85",
"view_tag": "b0"
}
}
}
],
"extra": [ 1, 224, 31, 28, 242, 5, 203, 29, 132, 247, 117, 19, 68, 161, 115, 168, 67, 18, 53, 123, 183, 220, 166, 2, 33, 36, 167, 32, 33, 79, 247, 26, 253, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}