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: 0f63d6476cc87489e9183a960800f5b71f77f0916b67692a2967a4bf138a410c
Tx prefix hash: b2ffbd90d5d2feae84f305b36c737b3f5e13608a269be3748d14a43f0ebeef7c
Tx public key: 63549e1e766432cbaf5f869efceb2776a6ed4763cddb496ca1aac5cd5639def0
| Timestamp: 1780859094 | Timestamp [UTC]: 2026-06-07 19:04:54 | Age [y:d:h:m:s]: 00:001:02:07:13 |
| Block: 7599 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 287 | RingCT/type: yes/0 |
| Extra: 0163549e1e766432cbaf5f869efceb2776a6ed4763cddb496ca1aac5cd5639def0020900000001e49593ff00 | ||
1 output(s) for total of 34.678155372246 HMNY
| stealth address | amount | amount idx | tag |
| 00: dc0e9fb796561c88e06574fcd7e0f14f98e92f77f1fb8de5aee9791546a627a8 | 34.678155372246 | 9389 of 0 | <3c> |
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": 7659,
"vin": [ {
"gen": {
"height": 7599
}
}
],
"vout": [ {
"amount": 34678155372246,
"target": {
"tagged_key": {
"key": "dc0e9fb796561c88e06574fcd7e0f14f98e92f77f1fb8de5aee9791546a627a8",
"view_tag": "3c"
}
}
}
],
"extra": [ 1, 99, 84, 158, 30, 118, 100, 50, 203, 175, 95, 134, 158, 252, 235, 39, 118, 166, 237, 71, 99, 205, 219, 73, 108, 161, 170, 197, 205, 86, 57, 222, 240, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}