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: 6413d309002afab8da42dc2f4ba2eecd45cef70039897d4c62fbb0da18868b6a
Tx prefix hash: 50b61303b6451cf568405b2f7fc3855d5de87c99344fb92cd050151ace6f4038
Tx public key: 2493d09403e97e46bdb8aac7643a15de29790c20ba831978aa0e3de636683f04
| Timestamp: 1780986973 | Timestamp [UTC]: 2026-06-09 06:36:13 | Age [y:d:h:m:s]: 00:000:08:12:42 |
| Block: 8160 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 479 | RingCT/type: yes/0 |
| Extra: 012493d09403e97e46bdb8aac7643a15de29790c20ba831978aa0e3de636683f04020900000002e49593ff00 | ||
1 output(s) for total of 34.641068772780 HMNY
| stealth address | amount | amount idx | tag |
| 00: bdac9cf2e6095fdd942b36750b160f444c0e91374ab867ec55bfbf0bb73b74e1 | 34.641068772780 | 10104 of 0 | <78> |
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": 8220,
"vin": [ {
"gen": {
"height": 8160
}
}
],
"vout": [ {
"amount": 34641068772780,
"target": {
"tagged_key": {
"key": "bdac9cf2e6095fdd942b36750b160f444c0e91374ab867ec55bfbf0bb73b74e1",
"view_tag": "78"
}
}
}
],
"extra": [ 1, 36, 147, 208, 148, 3, 233, 126, 70, 189, 184, 170, 199, 100, 58, 21, 222, 41, 121, 12, 32, 186, 131, 25, 120, 170, 14, 61, 230, 54, 104, 63, 4, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}