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: 78a1ec1af48fc695e990733c82a9f69b5da7d15174cfc7327854acd2eecb47b3
Tx prefix hash: e23a3010d071f542a7d8d172f9b87d60a7231d50d483bf4838517bf1be9297c8
Tx public key: c7d7e5e7fd34a72a7c82e97ae68288f5b8d3c8853ba4452f2138f9307b683e86
| Timestamp: 1780050870 | Timestamp [UTC]: 2026-05-29 10:34:30 | Age [y:d:h:m:s]: 00:010:12:44:23 |
| Block: 4390 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3496 | RingCT/type: yes/0 |
| Extra: 01c7d7e5e7fd34a72a7c82e97ae68288f5b8d3c8853ba4452f2138f9307b683e8602090000000326697be300 | ||
1 output(s) for total of 34.895280825811 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5f311ae8c0d3182623d2a95904cc5ab8d20779321d86cc512358cb94b154b398 | 34.895280825811 | 5491 of 0 | <64> |
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": 4450,
"vin": [ {
"gen": {
"height": 4390
}
}
],
"vout": [ {
"amount": 34895280825811,
"target": {
"tagged_key": {
"key": "5f311ae8c0d3182623d2a95904cc5ab8d20779321d86cc512358cb94b154b398",
"view_tag": "64"
}
}
}
],
"extra": [ 1, 199, 215, 229, 231, 253, 52, 167, 42, 124, 130, 233, 122, 230, 130, 136, 245, 184, 211, 200, 133, 59, 164, 69, 47, 33, 56, 249, 48, 123, 104, 62, 134, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}