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: f6813691c12d053f9fc6945837f0bbbc4807e5898e84c238c1d943b4b0bbdf83
Tx prefix hash: dd1c99d4e7a3006daa74f7e7b440192caed96d729bc443b57bd0b0318298048b
Tx public key: 54434aa8b7a89e8da95846e18a9cac31595fc00edd4270066e5b768f576e47b4
| Timestamp: 1779790903 | Timestamp [UTC]: 2026-05-26 10:21:43 | Age [y:d:h:m:s]: 00:013:15:14:14 |
| Block: 2223 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5663 | RingCT/type: yes/0 |
| Extra: 0154434aa8b7a89e8da95846e18a9cac31595fc00edd4270066e5b768f576e47b402090000000126697be300 | ||
1 output(s) for total of 35.035571591782 HMNY
| stealth address | amount | amount idx | tag |
| 00: 170af8d023d7dff88e3655c8a6c79fddc70640b5057b841e864c3ea6d7dc7881 | 35.035571591782 | 2575 of 0 | <36> |
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": 2283,
"vin": [ {
"gen": {
"height": 2223
}
}
],
"vout": [ {
"amount": 35035571591782,
"target": {
"tagged_key": {
"key": "170af8d023d7dff88e3655c8a6c79fddc70640b5057b841e864c3ea6d7dc7881",
"view_tag": "36"
}
}
}
],
"extra": [ 1, 84, 67, 74, 168, 183, 168, 158, 141, 169, 88, 70, 225, 138, 156, 172, 49, 89, 95, 192, 14, 221, 66, 112, 6, 110, 91, 118, 143, 87, 110, 71, 180, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}