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: 113623b74f0579d9d5a3b168b7deef992f713379ab1eca88262d48bed74c7ec9
Tx prefix hash: db65f32df846fa449a4814bdc8940797d5988a7345b8aa2a1776332682a6431e
Tx public key: e384fc8d3670b3b8ea4c63f2c01759b25a54c1ec368041e3cf1f31b836d3f1f1
| Timestamp: 1779869691 | Timestamp [UTC]: 2026-05-27 08:14:51 | Age [y:d:h:m:s]: 00:012:18:34:57 |
| Block: 2783 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5126 | RingCT/type: yes/0 |
| Extra: 01e384fc8d3670b3b8ea4c63f2c01759b25a54c1ec368041e3cf1f31b836d3f1f102090000000426697be300 | ||
1 output(s) for total of 34.998169506775 HMNY
| stealth address | amount | amount idx | tag |
| 00: b67a971384c5b662f2e405d241fee82f87ce1bff33485e02d7782ee7643c231e | 34.998169506775 | 3293 of 0 | <9e> |
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": 2843,
"vin": [ {
"gen": {
"height": 2783
}
}
],
"vout": [ {
"amount": 34998169506775,
"target": {
"tagged_key": {
"key": "b67a971384c5b662f2e405d241fee82f87ce1bff33485e02d7782ee7643c231e",
"view_tag": "9e"
}
}
}
],
"extra": [ 1, 227, 132, 252, 141, 54, 112, 179, 184, 234, 76, 99, 242, 192, 23, 89, 178, 90, 84, 193, 236, 54, 128, 65, 227, 207, 31, 49, 184, 54, 211, 241, 241, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}