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: e055e5ef2f02232b90248577750366bb190b0c0503d112e92c5ddc6fee00028a
Tx prefix hash: e28e7231b72ca45901f949c8b4f364e7731d55f3114ce21290d06d251fc60a13
Tx public key: ac126aba7867003f460f34f9a8d00649f72d8318ebfa7a1f6e022502f12c7f8f
| Timestamp: 1779473870 | Timestamp [UTC]: 2026-05-22 18:17:50 | Age [y:d:h:m:s]: 00:017:06:28:57 |
| Block: 596 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7290 | RingCT/type: yes/0 |
| Extra: 01ac126aba7867003f460f34f9a8d00649f72d8318ebfa7a1f6e022502f12c7f8f02090000000393369e7d00 | ||
1 output(s) for total of 35.144464925860 HMNY
| stealth address | amount | amount idx | tag |
| 00: af2264f7da521f59937ab1e0c918763ae013405885595fb0201b08b6e1bbdfa5 | 35.144464925860 | 610 of 0 | <c3> |
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": 656,
"vin": [ {
"gen": {
"height": 596
}
}
],
"vout": [ {
"amount": 35144464925860,
"target": {
"tagged_key": {
"key": "af2264f7da521f59937ab1e0c918763ae013405885595fb0201b08b6e1bbdfa5",
"view_tag": "c3"
}
}
}
],
"extra": [ 1, 172, 18, 106, 186, 120, 103, 0, 63, 70, 15, 52, 249, 168, 208, 6, 73, 247, 45, 131, 24, 235, 250, 122, 31, 110, 2, 37, 2, 241, 44, 127, 143, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}