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: 9ea89fd5433769106c9d7d33cab783ef87869a9386d5172e43b7bc52b720b3cb
Tx prefix hash: a8ca36f5319627cd8332d1fee94336d37ab953c695bf1876871ea237cea4c6b3
Tx public key: a5a236d0c33efb9cc7b7e9f0bf63575aa14cc03dc5d3d23bdefdad455b40cf04
| Timestamp: 1780860864 | Timestamp [UTC]: 2026-06-07 19:34:24 | Age [y:d:h:m:s]: 00:001:05:12:23 |
| Block: 7617 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 269 | RingCT/type: yes/0 |
| Extra: 01a5a236d0c33efb9cc7b7e9f0bf63575aa14cc03dc5d3d23bdefdad455b40cf04020900000004e49593ff00 | ||
1 output(s) for total of 34.676964811568 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1a50f0f5673302cf1ba2fbd26d73aa5e1d5d45ff699f434d8f069f7c96c0c09d | 34.676964811568 | 9413 of 0 | <c9> |
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": 7677,
"vin": [ {
"gen": {
"height": 7617
}
}
],
"vout": [ {
"amount": 34676964811568,
"target": {
"tagged_key": {
"key": "1a50f0f5673302cf1ba2fbd26d73aa5e1d5d45ff699f434d8f069f7c96c0c09d",
"view_tag": "c9"
}
}
}
],
"extra": [ 1, 165, 162, 54, 208, 195, 62, 251, 156, 199, 183, 233, 240, 191, 99, 87, 90, 161, 76, 192, 61, 197, 211, 210, 59, 222, 253, 173, 69, 91, 64, 207, 4, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}