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: 8d526067952df17cad81a59b78d6133a7d8a053a6f6c163fff989bd45c63e44b
Tx prefix hash: 286840bdcf00c8e974e9f32a4a62451be43b24f0e68c83bc5f9b56bad7004183
Tx public key: 66f30b0d1c2882d802d19d7017c710073d4415d157db3255e3881ee72b362093
| Timestamp: 1780803259 | Timestamp [UTC]: 2026-06-07 03:34:19 | Age [y:d:h:m:s]: 00:001:23:15:29 |
| Block: 6882 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1038 | RingCT/type: yes/0 |
| Extra: 0166f30b0d1c2882d802d19d7017c710073d4415d157db3255e3881ee72b362093020900000001e49593ff00 | ||
1 output(s) for total of 34.725612629859 HMNY
| stealth address | amount | amount idx | tag |
| 00: d626d6f222b21a30db6276ace167d9a77a9d4017f2a09a4ab07909b600d45801 | 34.725612629859 | 8494 of 0 | <00> |
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": 6942,
"vin": [ {
"gen": {
"height": 6882
}
}
],
"vout": [ {
"amount": 34725612629859,
"target": {
"tagged_key": {
"key": "d626d6f222b21a30db6276ace167d9a77a9d4017f2a09a4ab07909b600d45801",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 102, 243, 11, 13, 28, 40, 130, 216, 2, 209, 157, 112, 23, 199, 16, 7, 61, 68, 21, 209, 87, 219, 50, 85, 227, 136, 30, 231, 43, 54, 32, 147, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}