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: 6bbe5134f7959e5f8d64d34b54c04f871df52f70b914d569c4d473f9501c6f7c
Tx prefix hash: 0b7f634c3f999bd52ddcfd29d4fdc8d334bbc3399aad075862c72c98762a065a
Tx public key: e9db771dfd12d967d5be9dd000506b60fcaf7ed9ddac1bc4880c787c3e132709
| Timestamp: 1779866427 | Timestamp [UTC]: 2026-05-27 07:20:27 | Age [y:d:h:m:s]: 00:012:17:02:42 |
| Block: 2746 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5140 | RingCT/type: yes/0 |
| Extra: 01e9db771dfd12d967d5be9dd000506b60fcaf7ed9ddac1bc4880c787c3e13270902090000000226697be300 | ||
1 output(s) for total of 35.000639483583 HMNY
| stealth address | amount | amount idx | tag |
| 00: e9c405060f9e7f665aca9df4b91dcee07260eb9f7eff26510260febec24487c5 | 35.000639483583 | 3246 of 0 | <f3> |
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": 2806,
"vin": [ {
"gen": {
"height": 2746
}
}
],
"vout": [ {
"amount": 35000639483583,
"target": {
"tagged_key": {
"key": "e9c405060f9e7f665aca9df4b91dcee07260eb9f7eff26510260febec24487c5",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 233, 219, 119, 29, 253, 18, 217, 103, 213, 190, 157, 208, 0, 80, 107, 96, 252, 175, 126, 217, 221, 172, 27, 196, 136, 12, 120, 124, 62, 19, 39, 9, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}