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: 37693ba8e2ffaa735dde6069db23ed5ef444192aac43190d9a009c278387c8ef
Tx prefix hash: a793f1f167e3ae02e77f636c0c4d73cc5d93acb0f1195a047a1f5d946d025747
Tx public key: d9810c6178e49acc135d0cd110a01480fa8895a13e7869587ebfb7817aa64d41
| Timestamp: 1779851378 | Timestamp [UTC]: 2026-05-27 03:09:38 | Age [y:d:h:m:s]: 00:021:04:55:43 |
| Block: 2533 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6212 | RingCT/type: yes/0 |
| Extra: 01d9810c6178e49acc135d0cd110a01480fa8895a13e7869587ebfb7817aa64d4102090000000126697be300 | ||
1 output(s) for total of 35.024668329851 HMNY
| stealth address | amount | amount idx | tag |
| 00: e53dbcfa6a2c3be2b6800f6f2e6df08645c61f2792e6586819cad400a27c776a | 35.024668329851 | 2981 of 0 | <a4> |
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": 2593,
"vin": [ {
"gen": {
"height": 2533
}
}
],
"vout": [ {
"amount": 35024668329851,
"target": {
"tagged_key": {
"key": "e53dbcfa6a2c3be2b6800f6f2e6df08645c61f2792e6586819cad400a27c776a",
"view_tag": "a4"
}
}
}
],
"extra": [ 1, 217, 129, 12, 97, 120, 228, 154, 204, 19, 93, 12, 209, 16, 160, 20, 128, 250, 136, 149, 161, 62, 120, 105, 88, 126, 191, 183, 129, 122, 166, 77, 65, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}