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: e0262d87e70a3dcad5dd10d433c0cae532ba934f94d9ff8704b64d92b166b078
Tx prefix hash: ee93e0731ad67332ef1af3c8ff59a05e743be93ab8c468f746d5a12773494f41
Tx public key: 6ed8e60614fa29699d1322e0ab7f263c1d183343769b0bc54e86bfac84bbcaad
| Timestamp: 1779633395 | Timestamp [UTC]: 2026-05-24 14:36:35 | Age [y:d:h:m:s]: 00:015:10:10:12 |
| Block: 985 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6901 | RingCT/type: yes/0 |
| Extra: 016ed8e60614fa29699d1322e0ab7f263c1d183343769b0bc54e86bfac84bbcaad020900000002ba6d17be00 | ||
1 output(s) for total of 35.118398833545 HMNY
| stealth address | amount | amount idx | tag |
| 00: 057c015ea324737ee0b560ffce7a7535686ac7d7131a6cc4a44bdbaf1bfcae21 | 35.118398833545 | 1121 of 0 | <dc> |
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": 1045,
"vin": [ {
"gen": {
"height": 985
}
}
],
"vout": [ {
"amount": 35118398833545,
"target": {
"tagged_key": {
"key": "057c015ea324737ee0b560ffce7a7535686ac7d7131a6cc4a44bdbaf1bfcae21",
"view_tag": "dc"
}
}
}
],
"extra": [ 1, 110, 216, 230, 6, 20, 250, 41, 105, 157, 19, 34, 224, 171, 127, 38, 60, 29, 24, 51, 67, 118, 155, 11, 197, 78, 134, 191, 172, 132, 187, 202, 173, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}