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: dc6fa69df1f7a3cca2b5f4a5984eb79c90e7b0755741d34a67fd3f37afda0232
Tx prefix hash: 4a274e7fbb5bce61fe4a6b9ff168a2c60de26bda73b0ff52cc3e7d1eaaa1a99d
Tx public key: 0ea7d9d6c1d26ba141a4cf85370ff2a243f2f9a70a7f3d0cd12d4b2e8edcd16b
| Timestamp: 1779636743 | Timestamp [UTC]: 2026-05-24 15:32:23 | Age [y:d:h:m:s]: 00:016:01:36:40 |
| Block: 1136 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7598 | RingCT/type: yes/0 |
| Extra: 010ea7d9d6c1d26ba141a4cf85370ff2a243f2f9a70a7f3d0cd12d4b2e8edcd16b020900000001ba6d17be00 | ||
1 output(s) for total of 35.108285842760 HMNY
| stealth address | amount | amount idx | tag |
| 00: 24557161f01dc4a36d2de9ed096934c3d0cbee79262e6f9e2bd0241503634b23 | 35.108285842760 | 1278 of 0 | <b9> |
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": 1196,
"vin": [ {
"gen": {
"height": 1136
}
}
],
"vout": [ {
"amount": 35108285842760,
"target": {
"tagged_key": {
"key": "24557161f01dc4a36d2de9ed096934c3d0cbee79262e6f9e2bd0241503634b23",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 14, 167, 217, 214, 193, 210, 107, 161, 65, 164, 207, 133, 55, 15, 242, 162, 67, 242, 249, 167, 10, 127, 61, 12, 209, 45, 75, 46, 142, 220, 209, 107, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}