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: ad7c63528d4396eaf6c5cec1d15c32ddc2d851ffe72620af26b63f1a42615471
Tx prefix hash: f01f7ecc9f3757709d09186ef2eb11bf4a29645905ac525ad285c780098e8536
Tx public key: b4ba5a95abf001a029e69a59942d3d42acdb731d2e89c4dd1493bdc7a5f73157
| Timestamp: 1780689598 | Timestamp [UTC]: 2026-06-05 19:59:58 | Age [y:d:h:m:s]: 00:003:05:35:59 |
| Block: 5604 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2282 | RingCT/type: yes/0 |
| Extra: 01b4ba5a95abf001a029e69a59942d3d42acdb731d2e89c4dd1493bdc7a5f73157020900000001e49593ff00 | ||
1 output(s) for total of 34.849804421905 HMNY
| stealth address | amount | amount idx | tag |
| 00: 836389c5f211e8b34c6522209d390dc55ac0da55e928709b98ac13dd95527c3d | 34.849804421905 | 7049 of 0 | <30> |
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": 5664,
"vin": [ {
"gen": {
"height": 5604
}
}
],
"vout": [ {
"amount": 34849804421905,
"target": {
"tagged_key": {
"key": "836389c5f211e8b34c6522209d390dc55ac0da55e928709b98ac13dd95527c3d",
"view_tag": "30"
}
}
}
],
"extra": [ 1, 180, 186, 90, 149, 171, 240, 1, 160, 41, 230, 154, 89, 148, 45, 61, 66, 172, 219, 115, 29, 46, 137, 196, 221, 20, 147, 189, 199, 165, 247, 49, 87, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}