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: 44a4284f7368335395f901b4c7a7d612f318c92a735f8144b67ffa78729483c5
Tx prefix hash: aa85b4eac9e44aab22f6588f90efca64671ccbe6b7ccb05596257078523e7a68
Tx public key: 83f72e0ab65500012ec157344dec6f25e727a207e0570b4fc32005bcb49cdd3e
| Timestamp: 1779718448 | Timestamp [UTC]: 2026-05-25 14:14:08 | Age [y:d:h:m:s]: 00:014:09:04:45 |
| Block: 1703 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6183 | RingCT/type: yes/0 |
| Extra: 0183f72e0ab65500012ec157344dec6f25e727a207e0570b4fc32005bcb49cdd3e020900000001ba6d17be00 | ||
1 output(s) for total of 35.070337888844 HMNY
| stealth address | amount | amount idx | tag |
| 00: f0cd88537dcf1c6c7cf70dd3b0e73ddc32764e6a5e42a00462245c26bb640205 | 35.070337888844 | 1874 of 0 | <d8> |
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": 1763,
"vin": [ {
"gen": {
"height": 1703
}
}
],
"vout": [ {
"amount": 35070337888844,
"target": {
"tagged_key": {
"key": "f0cd88537dcf1c6c7cf70dd3b0e73ddc32764e6a5e42a00462245c26bb640205",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 131, 247, 46, 10, 182, 85, 0, 1, 46, 193, 87, 52, 77, 236, 111, 37, 231, 39, 162, 7, 224, 87, 11, 79, 195, 32, 5, 188, 180, 156, 221, 62, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}