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: 97135401ce3a24a52419f84bec468c5e1653fd421561851caaf01a3042e64ddf
Tx prefix hash: 92d385e41096293d776c0190d6cb717f46b047c7c6b2797ac8091fd9b09b1da0
Tx public key: d9b54cbd9eba0a8cad92bda37884ef4a2d7320a0e19a95e21be83f394452df0a
| Timestamp: 1780737058 | Timestamp [UTC]: 2026-06-06 09:10:58 | Age [y:d:h:m:s]: 00:002:15:35:49 |
| Block: 6371 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1515 | RingCT/type: yes/0 |
| Extra: 01d9b54cbd9eba0a8cad92bda37884ef4a2d7320a0e19a95e21be83f394452df0a020900000003e49593ff00 | ||
1 output(s) for total of 34.759474658606 HMNY
| stealth address | amount | amount idx | tag |
| 00: 10dde78cfe05aad593618ded715dfd6230f6f174d41ecf27c1cf919c91e5777f | 34.759474658606 | 7860 of 0 | <59> |
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": 6431,
"vin": [ {
"gen": {
"height": 6371
}
}
],
"vout": [ {
"amount": 34759474658606,
"target": {
"tagged_key": {
"key": "10dde78cfe05aad593618ded715dfd6230f6f174d41ecf27c1cf919c91e5777f",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 217, 181, 76, 189, 158, 186, 10, 140, 173, 146, 189, 163, 120, 132, 239, 74, 45, 115, 32, 160, 225, 154, 149, 226, 27, 232, 63, 57, 68, 82, 223, 10, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}