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: dca1b0647d93597ba248a351a7c57b63f63ad1c24443ac1200b1a8f7ff45e7f1
Tx prefix hash: 9ca2f471098aad61151510e8028ad93fcb7789b7079230578b3f7ba42548e743
Tx public key: f8514ea69a0e8f09fa3026575802ae9f77bac18c751ea367378864491ad13d36
| Timestamp: 1779443841 | Timestamp [UTC]: 2026-05-22 09:57:21 | Age [y:d:h:m:s]: 00:017:16:52:27 |
| Block: 243 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7677 | RingCT/type: yes/0 |
| Extra: 01f8514ea69a0e8f09fa3026575802ae9f77bac18c751ea367378864491ad13d360209000000014438f87f00 | ||
1 output(s) for total of 35.168135475896 HMNY
| stealth address | amount | amount idx | tag |
| 00: d6dfb4b14ff37c2b5c204db2dd5b351aca88edbfb492a767689be06a8c2d3c6b | 35.168135475896 | 239 of 0 | <a9> |
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": 303,
"vin": [ {
"gen": {
"height": 243
}
}
],
"vout": [ {
"amount": 35168135475896,
"target": {
"tagged_key": {
"key": "d6dfb4b14ff37c2b5c204db2dd5b351aca88edbfb492a767689be06a8c2d3c6b",
"view_tag": "a9"
}
}
}
],
"extra": [ 1, 248, 81, 78, 166, 154, 14, 143, 9, 250, 48, 38, 87, 88, 2, 174, 159, 119, 186, 193, 140, 117, 30, 163, 103, 55, 136, 100, 73, 26, 209, 61, 54, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}