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: 5be43015750382f32890288d6aca14ea176df221da6bb1893af6e91dd2dc92d7
Tx prefix hash: 96c2f79cd143109ca4922f40bf7405a3ea60bbf58f27a651bcc084c97ca681d9
Tx public key: 8fd0aaff9026a7b2b545dbfbb6d1042b25e7efaa386f5df691eeb99deefe1399
| Timestamp: 1780742833 | Timestamp [UTC]: 2026-06-06 10:47:13 | Age [y:d:h:m:s]: 00:002:16:02:35 |
| Block: 6425 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1474 | RingCT/type: yes/0 |
| Extra: 018fd0aaff9026a7b2b545dbfbb6d1042b25e7efaa386f5df691eeb99deefe1399020900000001e49593ff00 | ||
1 output(s) for total of 34.755894723987 HMNY
| stealth address | amount | amount idx | tag |
| 00: 93a7f940463d98405663843918e448681cb98e6d64366c9c29da64002000dfcd | 34.755894723987 | 7916 of 0 | <1c> |
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": 6485,
"vin": [ {
"gen": {
"height": 6425
}
}
],
"vout": [ {
"amount": 34755894723987,
"target": {
"tagged_key": {
"key": "93a7f940463d98405663843918e448681cb98e6d64366c9c29da64002000dfcd",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 143, 208, 170, 255, 144, 38, 167, 178, 181, 69, 219, 251, 182, 209, 4, 43, 37, 231, 239, 170, 56, 111, 93, 246, 145, 238, 185, 157, 238, 254, 19, 153, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}