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: b6989dc3614d174fa1d5ddb45a0b5a6b5ea213cc7742cc38d86ebc78b22abaf1
Tx prefix hash: 43ca445c457ba7154efd66eacfbeb650e853e17b4d1995d9fc06a0e4df92264a
Tx public key: f9156b4a46ff1b0fb961c459b2ec90b58e22abec56e2105d9a90e2c26756308e
| Timestamp: 1780997783 | Timestamp [UTC]: 2026-06-09 09:36:23 | Age [y:d:h:m:s]: 00:000:06:23:21 |
| Block: 8380 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 311 | RingCT/type: yes/0 |
| Extra: 01f9156b4a46ff1b0fb961c459b2ec90b58e22abec56e2105d9a90e2c26756308e020900000001e49593ff00 | ||
1 output(s) for total of 34.626535837329 HMNY
| stealth address | amount | amount idx | tag |
| 00: e180c55abce4174c648b55e13d0fb1327d8639d5031c6b87e75515b050e7bd7d | 34.626535837329 | 10360 of 0 | <ae> |
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": 8440,
"vin": [ {
"gen": {
"height": 8380
}
}
],
"vout": [ {
"amount": 34626535837329,
"target": {
"tagged_key": {
"key": "e180c55abce4174c648b55e13d0fb1327d8639d5031c6b87e75515b050e7bd7d",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 249, 21, 107, 74, 70, 255, 27, 15, 185, 97, 196, 89, 178, 236, 144, 181, 142, 34, 171, 236, 86, 226, 16, 93, 154, 144, 226, 194, 103, 86, 48, 142, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}