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: 1778b28ccfbde1511b84f59074c03aa611856913267c6f40645bc2dc4ec12be6
Tx prefix hash: 44c03adc81a2dc62477be14e79e394ac60233adc392846786e66bcb66a23c899
Tx public key: d1ab69ddefd436961b8e9c5b8996be0574e99931c9a6161f0126f21d784bb42d
| Timestamp: 1780980123 | Timestamp [UTC]: 2026-06-09 04:42:03 | Age [y:d:h:m:s]: 00:000:06:44:45 |
| Block: 8012 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 503 | RingCT/type: yes/0 |
| Extra: 01d1ab69ddefd436961b8e9c5b8996be0574e99931c9a6161f0126f21d784bb42d020900000001e49593ff00 | ||
1 output(s) for total of 34.650848906532 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9c749a1953eb7b60af7473a2b6c78755eddc85d794ac2c7321ef637401dbbfce | 34.650848906532 | 9934 of 0 | <3b> |
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": 8072,
"vin": [ {
"gen": {
"height": 8012
}
}
],
"vout": [ {
"amount": 34650848906532,
"target": {
"tagged_key": {
"key": "9c749a1953eb7b60af7473a2b6c78755eddc85d794ac2c7321ef637401dbbfce",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 209, 171, 105, 221, 239, 212, 54, 150, 27, 142, 156, 91, 137, 150, 190, 5, 116, 233, 153, 49, 201, 166, 22, 31, 1, 38, 242, 29, 120, 75, 180, 45, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}