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: c4e21c504abce435620ef781be7080394c21aceee08632ef3ca015560bb2ad09
Tx prefix hash: d5bf18098f84a4f3054d1914afc330a67a1387bdb9aedb57637b59c36336450b
Tx public key: 0fd9426d15115f87321d9fa356c3cd2a188f2a90a5be7b995bcb0c48d77c43ff
| Timestamp: 1779470750 | Timestamp [UTC]: 2026-05-22 17:25:50 | Age [y:d:h:m:s]: 00:017:09:14:46 |
| Block: 558 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7339 | RingCT/type: yes/0 |
| Extra: 010fd9426d15115f87321d9fa356c3cd2a188f2a90a5be7b995bcb0c48d77c43ff02090000000193369e7d00 | ||
1 output(s) for total of 35.147012264993 HMNY
| stealth address | amount | amount idx | tag |
| 00: a219dcc72d3dcda66c9436b4f44db6a377ab53811698003b39de2cafec2df39e | 35.147012264993 | 566 of 0 | <0b> |
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": 618,
"vin": [ {
"gen": {
"height": 558
}
}
],
"vout": [ {
"amount": 35147012264993,
"target": {
"tagged_key": {
"key": "a219dcc72d3dcda66c9436b4f44db6a377ab53811698003b39de2cafec2df39e",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 15, 217, 66, 109, 21, 17, 95, 135, 50, 29, 159, 163, 86, 195, 205, 42, 24, 143, 42, 144, 165, 190, 123, 153, 91, 203, 12, 72, 215, 124, 67, 255, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}