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: ec320d9afb89475f2722ecde89daa602dbd89d5f089a0b2869e60bac3d7e43ce
Tx prefix hash: 3489fc4036c3518a0e7c8ecaeaf3a7f1d5b756c4dcca1f5c6b2d7989374f9317
Tx public key: baf41809167a65b9427336f22299daad2478b3f685c9e607c925de3062be5c23
| Timestamp: 1780807528 | Timestamp [UTC]: 2026-06-07 04:45:28 | Age [y:d:h:m:s]: 00:001:16:26:39 |
| Block: 6966 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 920 | RingCT/type: yes/0 |
| Extra: 01baf41809167a65b9427336f22299daad2478b3f685c9e607c925de3062be5c23020900000002e49593ff00 | ||
1 output(s) for total of 34.720049426845 HMNY
| stealth address | amount | amount idx | tag |
| 00: 818fbe47883c2645675ec60285e317d0c98aecfc924e39400042989a5f784efe | 34.720049426845 | 8592 of 0 | <75> |
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": 7026,
"vin": [ {
"gen": {
"height": 6966
}
}
],
"vout": [ {
"amount": 34720049426845,
"target": {
"tagged_key": {
"key": "818fbe47883c2645675ec60285e317d0c98aecfc924e39400042989a5f784efe",
"view_tag": "75"
}
}
}
],
"extra": [ 1, 186, 244, 24, 9, 22, 122, 101, 185, 66, 115, 54, 242, 34, 153, 218, 173, 36, 120, 179, 246, 133, 201, 230, 7, 201, 37, 222, 48, 98, 190, 92, 35, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}