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: ca1ae9088a43cfb003055fe4cc9a8bd618a929464a42b13246eb90911959dfca
Tx prefix hash: 08f81e8b3eae6c8468480653f91211bf9a7f54e4bd0a505774e2ecbdbfffe759
Tx public key: 4d8b859fe9f377f16485a8ec85f44dad187939cbf0ffff91b5c718a446a95bc7
| Timestamp: 1779722759 | Timestamp [UTC]: 2026-05-25 15:25:59 | Age [y:d:h:m:s]: 00:014:10:09:58 |
| Block: 1786 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6100 | RingCT/type: yes/0 |
| Extra: 014d8b859fe9f377f16485a8ec85f44dad187939cbf0ffff91b5c718a446a95bc7020900000001ba6d17be00 | ||
1 output(s) for total of 35.064786340028 HMNY
| stealth address | amount | amount idx | tag |
| 00: dacc22fce0c2e18071e3d3da42d78c1a86804703095aa28bcbe824de7dd50bdd | 35.064786340028 | 1973 of 0 | <e1> |
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": 1846,
"vin": [ {
"gen": {
"height": 1786
}
}
],
"vout": [ {
"amount": 35064786340028,
"target": {
"tagged_key": {
"key": "dacc22fce0c2e18071e3d3da42d78c1a86804703095aa28bcbe824de7dd50bdd",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 77, 139, 133, 159, 233, 243, 119, 241, 100, 133, 168, 236, 133, 244, 77, 173, 24, 121, 57, 203, 240, 255, 255, 145, 181, 199, 24, 164, 70, 169, 91, 199, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}