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: 26ffd2d0bcdc16e78bd4e4fadb868ec5a05b52c30d07ce1a9495b6597510725c
Tx prefix hash: c69e428870ad5d58e29fba6e4d25ba139ee4084d365f04cf9fa620c660508ad2
Tx public key: b9ed24134b956621283e987ef3c2aa2d3b5671264c6370ea796c0d36c2a398da
| Timestamp: 1780693110 | Timestamp [UTC]: 2026-06-05 20:58:30 | Age [y:d:h:m:s]: 00:011:12:16:36 |
| Block: 5847 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2898 | RingCT/type: yes/0 |
| Extra: 01b9ed24134b956621283e987ef3c2aa2d3b5671264c6370ea796c0d36c2a398da020900000001e49593ff00 | ||
1 output(s) for total of 34.794232438913 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c3a43bec72ba0761c557a18311f162708f0739988885b9ee6d01976ff7c7845 | 34.794232438913 | 7304 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": 5907,
"vin": [ {
"gen": {
"height": 5847
}
}
],
"vout": [ {
"amount": 34794232438913,
"target": {
"tagged_key": {
"key": "2c3a43bec72ba0761c557a18311f162708f0739988885b9ee6d01976ff7c7845",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 185, 237, 36, 19, 75, 149, 102, 33, 40, 62, 152, 126, 243, 194, 170, 45, 59, 86, 113, 38, 76, 99, 112, 234, 121, 108, 13, 54, 194, 163, 152, 218, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}