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: 1e1bbec22b451672bcec9f5209c44bdcb99e1f73fe6293cb7c82a28ce66011b5
Tx prefix hash: 2c58d4a53884a3c98f97c68319b2f75fffc964fc9fa40ac96aa73f19126e942d
Tx public key: 41d22c15f9d8fef3a6ad8435e829aff6cf5fe2403d250164ca91ffb88c009304
| Timestamp: 1780393715 | Timestamp [UTC]: 2026-06-02 09:48:35 | Age [y:d:h:m:s]: 00:006:17:50:15 |
| Block: 5229 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2713 | RingCT/type: yes/0 |
| Extra: 0141d22c15f9d8fef3a6ad8435e829aff6cf5fe2403d250164ca91ffb88c00930402090000000126697be300 | ||
1 output(s) for total of 34.840283663847 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5eb967b936caaab77ad4f86a0918efc3096524aa7e5b704f93b2c8490e1ec62b | 34.840283663847 | 6618 of 0 | <52> |
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": 5289,
"vin": [ {
"gen": {
"height": 5229
}
}
],
"vout": [ {
"amount": 34840283663847,
"target": {
"tagged_key": {
"key": "5eb967b936caaab77ad4f86a0918efc3096524aa7e5b704f93b2c8490e1ec62b",
"view_tag": "52"
}
}
}
],
"extra": [ 1, 65, 210, 44, 21, 249, 216, 254, 243, 166, 173, 132, 53, 232, 41, 175, 246, 207, 95, 226, 64, 61, 37, 1, 100, 202, 145, 255, 184, 140, 0, 147, 4, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}