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: d20ff891db6203a50a94521bda370b2ccfbb5e96323c7faed2770b087c0282f4
Tx prefix hash: 28bbe7bff9f893d55ad1225a6cb6a9c78e7dd21b8ec504f38aeb5591c2639187
Tx public key: f256ee45beed123f0d8c0f15a3be1b1384c5d39f60d09482d776ad4090cddb86
| Timestamp: 1781020279 | Timestamp [UTC]: 2026-06-09 15:51:19 | Age [y:d:h:m:s]: 00:007:17:23:47 |
| Block: 8683 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 62 | RingCT/type: yes/0 |
| Extra: 01f256ee45beed123f0d8c0f15a3be1b1384c5d39f60d09482d776ad4090cddb86020900000004e49593ff00 | ||
1 output(s) for total of 34.606530002395 HMNY
| stealth address | amount | amount idx | tag |
| 00: ab5a4fe9567ceb52b60f8ff2467542782650031e56eecc96d64e803409ef1ecf | 34.606530002395 | 10737 of 0 | <57> |
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": 8743,
"vin": [ {
"gen": {
"height": 8683
}
}
],
"vout": [ {
"amount": 34606530002395,
"target": {
"tagged_key": {
"key": "ab5a4fe9567ceb52b60f8ff2467542782650031e56eecc96d64e803409ef1ecf",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 242, 86, 238, 69, 190, 237, 18, 63, 13, 140, 15, 21, 163, 190, 27, 19, 132, 197, 211, 159, 96, 208, 148, 130, 215, 118, 173, 64, 144, 205, 219, 134, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}