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: 8d7dba7fa3385a4ccfc09a9735ca7af3d1371ab376bd2279a9eb815d683cebe7
Tx prefix hash: e407243de7775f07e112ff98f1b14fdbe996cb39bf03cbfee2866b7ef39459bd
Tx public key: 80b644065a8ff88a43c0327bbcccecf9c8d0a695d5772bd5fa3b81c19e47e964
| Timestamp: 1779647120 | Timestamp [UTC]: 2026-05-24 18:25:20 | Age [y:d:h:m:s]: 00:015:22:43:43 |
| Block: 1457 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7277 | RingCT/type: yes/0 |
| Extra: 0180b644065a8ff88a43c0327bbcccecf9c8d0a695d5772bd5fa3b81c19e47e964020900000002ba6d17be00 | ||
1 output(s) for total of 35.086797040431 HMNY
| stealth address | amount | amount idx | tag |
| 00: 623cd1e5e89085c2c2988a243e9c319ee5bfc73bef8a4821890d26320334bd46 | 35.086797040431 | 1611 of 0 | <e4> |
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": 1517,
"vin": [ {
"gen": {
"height": 1457
}
}
],
"vout": [ {
"amount": 35086797040431,
"target": {
"tagged_key": {
"key": "623cd1e5e89085c2c2988a243e9c319ee5bfc73bef8a4821890d26320334bd46",
"view_tag": "e4"
}
}
}
],
"extra": [ 1, 128, 182, 68, 6, 90, 143, 248, 138, 67, 192, 50, 123, 188, 204, 236, 249, 200, 208, 166, 149, 213, 119, 43, 213, 250, 59, 129, 193, 158, 71, 233, 100, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}