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: 8885cfdd12d37a4d8fa9f5c6076fc73a75ffd05ccec11c6f664df379384d6122
Tx prefix hash: 82bd9aa2f655a9511078210cbcd2e1d6a22a46832669608fde5270f2b0643fa2
Tx public key: 2996fb33842262f9c14699d01477db975232eea1b176e515e43e636efe554d31
| Timestamp: 1780977652 | Timestamp [UTC]: 2026-06-09 04:00:52 | Age [y:d:h:m:s]: 00:000:08:32:35 |
| Block: 7959 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 612 | RingCT/type: yes/0 |
| Extra: 012996fb33842262f9c14699d01477db975232eea1b176e515e43e636efe554d31020900000001e49593ff00 | ||
1 output(s) for total of 34.654351923141 HMNY
| stealth address | amount | amount idx | tag |
| 00: d173bf2d53ed29535b525023e72549a9e9d301914c57d34d04dbdeab4afda4a2 | 34.654351923141 | 9873 of 0 | <a5> |
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": 8019,
"vin": [ {
"gen": {
"height": 7959
}
}
],
"vout": [ {
"amount": 34654351923141,
"target": {
"tagged_key": {
"key": "d173bf2d53ed29535b525023e72549a9e9d301914c57d34d04dbdeab4afda4a2",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 41, 150, 251, 51, 132, 34, 98, 249, 193, 70, 153, 208, 20, 119, 219, 151, 82, 50, 238, 161, 177, 118, 229, 21, 228, 62, 99, 110, 254, 85, 77, 49, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}