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: f51eb46f8288bcdc22df4d00d82245404abe4b4945768acbe955f662b98bf85c
Tx prefix hash: 7ef9c4d3566f3911784421753eb2c0ad1556044a51e3a3f34826368eee55f102
Tx public key: 03c5a47dc5fad694fae185050f2bb42194dc3dc56bfbc0271adb903d1ffea010
| Timestamp: 1779855085 | Timestamp [UTC]: 2026-05-27 04:11:25 | Age [y:d:h:m:s]: 00:012:20:35:22 |
| Block: 2605 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5281 | RingCT/type: yes/0 |
| Extra: 0103c5a47dc5fad694fae185050f2bb42194dc3dc56bfbc0271adb903d1ffea01002090000000126697be300 | ||
1 output(s) for total of 35.010053695898 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4957775de63c0f691dc7df96198e8e04fa3f31511b2a5aea0106cf998316fe75 | 35.010053695898 | 3067 of 0 | <a8> |
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": 2665,
"vin": [ {
"gen": {
"height": 2605
}
}
],
"vout": [ {
"amount": 35010053695898,
"target": {
"tagged_key": {
"key": "4957775de63c0f691dc7df96198e8e04fa3f31511b2a5aea0106cf998316fe75",
"view_tag": "a8"
}
}
}
],
"extra": [ 1, 3, 197, 164, 125, 197, 250, 214, 148, 250, 225, 133, 5, 15, 43, 180, 33, 148, 220, 61, 197, 107, 251, 192, 39, 26, 219, 144, 61, 31, 254, 160, 16, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}