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: 423466334f229d941721b1506a8a344db54647fe0687711238ce888087dcb8a4
Tx prefix hash: 5c4871175758f73fae853c0b3b0179cbbda45d85acd259db0dff0b04a2644397
Tx public key: 95de571cfffebda06cafac9e2c966f6a451fd09689348742518b14c004c42fba
| Timestamp: 1781005393 | Timestamp [UTC]: 2026-06-09 11:43:13 | Age [y:d:h:m:s]: 00:007:21:31:53 |
| Block: 8531 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 214 | RingCT/type: yes/0 |
| Extra: 0195de571cfffebda06cafac9e2c966f6a451fd09689348742518b14c004c42fba020900000002e49593ff00 | ||
1 output(s) for total of 34.616564487567 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1b1d35bfde46eae1bde0c2f1524c0875ba3cc82a6d81a9f9b87c925f1211b320 | 34.616564487567 | 10537 of 0 | <1e> |
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": 8591,
"vin": [ {
"gen": {
"height": 8531
}
}
],
"vout": [ {
"amount": 34616564487567,
"target": {
"tagged_key": {
"key": "1b1d35bfde46eae1bde0c2f1524c0875ba3cc82a6d81a9f9b87c925f1211b320",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 149, 222, 87, 28, 255, 254, 189, 160, 108, 175, 172, 158, 44, 150, 111, 106, 69, 31, 208, 150, 137, 52, 135, 66, 81, 139, 20, 192, 4, 196, 47, 186, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}