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: 4ca72f6b6d99c4273af361946bdf5159679e4638a88e45502b15df99ca0e8ead
Tx prefix hash: 1596e3c0e61aa4dae3cf1e963ff9d331541b4a0768317b459a119586286f1eda
Tx public key: d3055ff8b1adf96e9a9ce86781d3348ebbd1c0072abd460931e11294f9f88e99
| Timestamp: 1780770279 | Timestamp [UTC]: 2026-06-06 18:24:39 | Age [y:d:h:m:s]: 00:002:07:11:18 |
| Block: 6658 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1228 | RingCT/type: yes/0 |
| Extra: 01d3055ff8b1adf96e9a9ce86781d3348ebbd1c0072abd460931e11294f9f88e99020900000004e49593ff00 | ||
1 output(s) for total of 34.740452196208 HMNY
| stealth address | amount | amount idx | tag |
| 00: 17a3008719f4f845859f9245cdf29530fc0e5d4138fd2d5bf3257ec3b82731df | 34.740452196208 | 8210 of 0 | <f2> |
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": 6718,
"vin": [ {
"gen": {
"height": 6658
}
}
],
"vout": [ {
"amount": 34740452196208,
"target": {
"tagged_key": {
"key": "17a3008719f4f845859f9245cdf29530fc0e5d4138fd2d5bf3257ec3b82731df",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 211, 5, 95, 248, 177, 173, 249, 110, 154, 156, 232, 103, 129, 211, 52, 142, 187, 209, 192, 7, 42, 189, 70, 9, 49, 225, 18, 148, 249, 248, 142, 153, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}