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: 2101e872ca29ec224b15ba970e3a637f95100f363df28bf97f5e8ad16ec16a77
Tx prefix hash: 3ef22b0425db6e39f54a2874b3d063502412401bb05def0a5b0572804d1275fc
Tx public key: 12ee9e3dca3bcdf05622f9ea0c9648abfee951cb393733c40a678b07ede8cbd7
| Timestamp: 1780691540 | Timestamp [UTC]: 2026-06-05 20:32:20 | Age [y:d:h:m:s]: 00:003:06:17:28 |
| Block: 5735 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2165 | RingCT/type: yes/0 |
| Extra: 0112ee9e3dca3bcdf05622f9ea0c9648abfee951cb393733c40a678b07ede8cbd7020900000001e49593ff00 | ||
1 output(s) for total of 34.801666089921 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3f01e94643e12d50a2058327bb9c9068e524d41e33f7745d6626f69638d837cf | 34.801666089921 | 7188 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": 5795,
"vin": [ {
"gen": {
"height": 5735
}
}
],
"vout": [ {
"amount": 34801666089921,
"target": {
"tagged_key": {
"key": "3f01e94643e12d50a2058327bb9c9068e524d41e33f7745d6626f69638d837cf",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 18, 238, 158, 61, 202, 59, 205, 240, 86, 34, 249, 234, 12, 150, 72, 171, 254, 233, 81, 203, 57, 55, 51, 196, 10, 103, 139, 7, 237, 232, 203, 215, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}