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: 0ec0dc5667583de9454b731a9d08c2821537bca8902c3d4733dc9642cebcde92
Tx prefix hash: 9cf7bf0722bef1c987cc7bc37e28c639bd3dbbb628990d556cd13252706ee9c5
Tx public key: 3c7a96d713fc26f6102eb287b321aa03711a8ba21f4a204e68147b249313ab86
| Timestamp: 1779779267 | Timestamp [UTC]: 2026-05-26 07:07:47 | Age [y:d:h:m:s]: 00:013:19:32:49 |
| Block: 2087 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5810 | RingCT/type: yes/0 |
| Extra: 013c7a96d713fc26f6102eb287b321aa03711a8ba21f4a204e68147b249313ab8602090000000126697be300 | ||
1 output(s) for total of 35.044660986033 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f5e8e88fffa697d7ce2252ea435cb3e103d1d80dd61be726667bb18148a038c | 35.044660986033 | 2399 of 0 | <d5> |
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": 2147,
"vin": [ {
"gen": {
"height": 2087
}
}
],
"vout": [ {
"amount": 35044660986033,
"target": {
"tagged_key": {
"key": "8f5e8e88fffa697d7ce2252ea435cb3e103d1d80dd61be726667bb18148a038c",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 60, 122, 150, 215, 19, 252, 38, 246, 16, 46, 178, 135, 179, 33, 170, 3, 113, 26, 139, 162, 31, 74, 32, 78, 104, 20, 123, 36, 147, 19, 171, 134, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}