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: 37d526066f976d7a0937bc6acd15297c9724befadb224ccfbff035cca88fb43b
Tx prefix hash: 7f1bc40172b98132a560c17aa703a2197f65e8da33d746f9ec7fea3f94813493
Tx public key: 7389991c3c979327f22f304b063b040eb7130b5128392ea95bbf55dad91f5e9c
| Timestamp: 1779437749 | Timestamp [UTC]: 2026-05-22 08:15:49 | Age [y:d:h:m:s]: 00:017:17:20:08 |
| Block: 173 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7713 | RingCT/type: yes/0 |
| Extra: 017389991c3c979327f22f304b063b040eb7130b5128392ea95bbf55dad91f5e9c020900000001a662ed0300 | ||
1 output(s) for total of 35.172831246502 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4ab0978aa03a04bda9c258a38afab4bc349e0268bb7d64ac317e1f7d4a166a7f | 35.172831246502 | 169 of 0 | <51> |
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": 233,
"vin": [ {
"gen": {
"height": 173
}
}
],
"vout": [ {
"amount": 35172831246502,
"target": {
"tagged_key": {
"key": "4ab0978aa03a04bda9c258a38afab4bc349e0268bb7d64ac317e1f7d4a166a7f",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 115, 137, 153, 28, 60, 151, 147, 39, 242, 47, 48, 75, 6, 59, 4, 14, 183, 19, 11, 81, 40, 57, 46, 169, 91, 191, 85, 218, 217, 31, 94, 156, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}