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: b5a34a57f7c1d11792aad2c7f7cd1bcece8107283f92b7c4463ffccee18a1afd
Tx prefix hash: 3478ab259869e775573c119777c6950ef9d81c1723c1f6bb47959c106ed55723
Tx public key: 84b283c6fb0c974d1f017e92451ba6268451891a6788bb72d9b36bd3cd05c10b
| Timestamp: 1779951154 | Timestamp [UTC]: 2026-05-28 06:52:34 | Age [y:d:h:m:s]: 00:011:16:26:19 |
| Block: 3628 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4258 | RingCT/type: yes/0 |
| Extra: 0184b283c6fb0c974d1f017e92451ba6268451891a6788bb72d9b36bd3cd05c10b02090000000326697be300 | ||
1 output(s) for total of 34.941807998824 HMNY
| stealth address | amount | amount idx | tag |
| 00: f73ed59de050786097ae2465f9920227c31edf4fe158d209f11c80d568f1a369 | 34.941807998824 | 4381 of 0 | <b6> |
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": 3688,
"vin": [ {
"gen": {
"height": 3628
}
}
],
"vout": [ {
"amount": 34941807998824,
"target": {
"tagged_key": {
"key": "f73ed59de050786097ae2465f9920227c31edf4fe158d209f11c80d568f1a369",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 132, 178, 131, 198, 251, 12, 151, 77, 31, 1, 126, 146, 69, 27, 166, 38, 132, 81, 137, 26, 103, 136, 187, 114, 217, 179, 107, 211, 205, 5, 193, 11, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}