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: 1433175c8eadc78b651d461d44d1cd0ddcfcae38992455de0b0999a147ddb826
Tx prefix hash: 0c3c200cb82c6eb2f4a8f1ee87fb9951a48067bcf8d7538de97e91deda65e1d1
Tx public key: e726d433d33e294033fbe6c07098c6b4d896736e6c2590e7a79b0785b38127ad
| Timestamp: 1779480163 | Timestamp [UTC]: 2026-05-22 20:02:43 | Age [y:d:h:m:s]: 00:017:03:16:10 |
| Block: 642 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7244 | RingCT/type: yes/0 |
| Extra: 01e726d433d33e294033fbe6c07098c6b4d896736e6c2590e7a79b0785b38127ad02090000000293369e7d00 | ||
1 output(s) for total of 35.147854351818 HMNY
| stealth address | amount | amount idx | tag |
| 00: eef39ee62d87b0d2fbe03b583e40391400a8cbbfea80fce48afe5d65c7428797 | 35.147854351818 | 682 of 0 | <e0> |
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": 702,
"vin": [ {
"gen": {
"height": 642
}
}
],
"vout": [ {
"amount": 35147854351818,
"target": {
"tagged_key": {
"key": "eef39ee62d87b0d2fbe03b583e40391400a8cbbfea80fce48afe5d65c7428797",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 231, 38, 212, 51, 211, 62, 41, 64, 51, 251, 230, 192, 112, 152, 198, 180, 216, 150, 115, 110, 108, 37, 144, 231, 167, 155, 7, 133, 179, 129, 39, 173, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}