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: dd93177c7ecad2d0e79efe5d7b7d1b454cc0e52e202bac8bc177022f5c03323b
Tx prefix hash: ef31a9759f298846e0504e2093b4b5a2d0de592c679d0a8aa9bf9397cce47c23
Tx public key: 3a703b532e260cd0112ce49f07d1d30df4c25c3b703821bea26ce883859ea83d
| Timestamp: 1779806502 | Timestamp [UTC]: 2026-05-26 14:41:42 | Age [y:d:h:m:s]: 00:013:10:54:15 |
| Block: 2353 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5533 | RingCT/type: yes/0 |
| Extra: 013a703b532e260cd0112ce49f07d1d30df4c25c3b703821bea26ce883859ea83d02090000000126697be300 | ||
1 output(s) for total of 35.026885403991 HMNY
| stealth address | amount | amount idx | tag |
| 00: 80141fd99b5d9c8eca0c1e872d8e96d1ce24f1117dc066d3994f01a705b52c37 | 35.026885403991 | 2757 of 0 | <df> |
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": 2413,
"vin": [ {
"gen": {
"height": 2353
}
}
],
"vout": [ {
"amount": 35026885403991,
"target": {
"tagged_key": {
"key": "80141fd99b5d9c8eca0c1e872d8e96d1ce24f1117dc066d3994f01a705b52c37",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 58, 112, 59, 83, 46, 38, 12, 208, 17, 44, 228, 159, 7, 209, 211, 13, 244, 194, 92, 59, 112, 56, 33, 190, 162, 108, 232, 131, 133, 158, 168, 61, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}