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: 42a67001a0385376748f83f8f208a8de6f3bdf9be3fa95fc766f9c6ae2eeda68
Tx prefix hash: 1bf1ee27e474a1532351ae3dcb83df580a2da1b2156471b423ceae3603f96c39
Tx public key: 23c15396a2834e3fd4dd7c396b2b6dfa21c8e5d356e2af847d0b41d512ca7212
| Timestamp: 1780805375 | Timestamp [UTC]: 2026-06-07 04:09:35 | Age [y:d:h:m:s]: 00:001:21:26:22 |
| Block: 6934 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 952 | RingCT/type: yes/0 |
| Extra: 0123c15396a2834e3fd4dd7c396b2b6dfa21c8e5d356e2af847d0b41d512ca7212020900000001e49593ff00 | ||
1 output(s) for total of 34.736008237181 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5c15a63f5f72030f144557c7c4f6f9ac3445d3ca476286523b659d4328042a6b | 34.736008237181 | 8552 of 0 | <04> |
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": 6994,
"vin": [ {
"gen": {
"height": 6934
}
}
],
"vout": [ {
"amount": 34736008237181,
"target": {
"tagged_key": {
"key": "5c15a63f5f72030f144557c7c4f6f9ac3445d3ca476286523b659d4328042a6b",
"view_tag": "04"
}
}
}
],
"extra": [ 1, 35, 193, 83, 150, 162, 131, 78, 63, 212, 221, 124, 57, 107, 43, 109, 250, 33, 200, 229, 211, 86, 226, 175, 132, 125, 11, 65, 213, 18, 202, 114, 18, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}