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: d7e208a43dcb6626f66e38c3052c61d7c6598e17837b2b0781ef301bd3c20038
Tx prefix hash: bc39b4dd24ef400f387aa536b2dfd4feffa196c7a4a728c062b6e1f1ed03bd39
Tx public key: fe0ad5a7bca6e78783e8bd86f1385fd9e5a839e186badf7b36754cbc1e627115
| Timestamp: 1780800133 | Timestamp [UTC]: 2026-06-07 02:42:13 | Age [y:d:h:m:s]: 00:001:22:04:34 |
| Block: 6822 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1064 | RingCT/type: yes/0 |
| Extra: 01fe0ad5a7bca6e78783e8bd86f1385fd9e5a839e186badf7b36754cbc1e627115020900000002e49593ff00 | ||
1 output(s) for total of 34.729586892041 HMNY
| stealth address | amount | amount idx | tag |
| 00: 074a8cc1fce5ed9f307eb32b61ca8d45864abf2699f7e8412b6daa9bd7466c3a | 34.729586892041 | 8424 of 0 | <07> |
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": 6882,
"vin": [ {
"gen": {
"height": 6822
}
}
],
"vout": [ {
"amount": 34729586892041,
"target": {
"tagged_key": {
"key": "074a8cc1fce5ed9f307eb32b61ca8d45864abf2699f7e8412b6daa9bd7466c3a",
"view_tag": "07"
}
}
}
],
"extra": [ 1, 254, 10, 213, 167, 188, 166, 231, 135, 131, 232, 189, 134, 241, 56, 95, 217, 229, 168, 57, 225, 134, 186, 223, 123, 54, 117, 76, 188, 30, 98, 113, 21, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}