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: 7c1167f5c46bd4f1b0044700ae393181890c41338aa31715485639f94cef53ae
Tx prefix hash: a50cc7c5d4f207d50bce304019882c41840ea07ceaf472e72cf3ce0f0f5462e7
Tx public key: 8c15c221b9174294b8465159d47bd9947c02970a1624c188b811303daa23aa9b
| Timestamp: 1780986422 | Timestamp [UTC]: 2026-06-09 06:27:02 | Age [y:d:h:m:s]: 00:000:05:07:32 |
| Block: 8151 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 365 | RingCT/type: yes/0 |
| Extra: 018c15c221b9174294b8465159d47bd9947c02970a1624c188b811303daa23aa9b020900000001e49593ff00 | ||
1 output(s) for total of 34.641663431808 HMNY
| stealth address | amount | amount idx | tag |
| 00: 94b4f5b6c55ec234222baf51ec6814fd87c1c0febcc48eefa99fc02eda49c184 | 34.641663431808 | 10093 of 0 | <9c> |
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": 8211,
"vin": [ {
"gen": {
"height": 8151
}
}
],
"vout": [ {
"amount": 34641663431808,
"target": {
"tagged_key": {
"key": "94b4f5b6c55ec234222baf51ec6814fd87c1c0febcc48eefa99fc02eda49c184",
"view_tag": "9c"
}
}
}
],
"extra": [ 1, 140, 21, 194, 33, 185, 23, 66, 148, 184, 70, 81, 89, 212, 123, 217, 148, 124, 2, 151, 10, 22, 36, 193, 136, 184, 17, 48, 61, 170, 35, 170, 155, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}