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: 3c59ff10b484a4538bcad8f622df03881a8835bc82c68b0cfa13c99c463ea926
Tx prefix hash: 4e861477cf6da085cf42cb986d09a1a1a23b571225f6bbad84508bd3c3cb4b2b
Tx public key: 735a983ebc857eb3dac7f7b3aa9db81489a8380b8e509cd8f439079c22db3754
| Timestamp: 1779471494 | Timestamp [UTC]: 2026-05-22 17:38:14 | Age [y:d:h:m:s]: 00:017:07:08:33 |
| Block: 570 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7316 | RingCT/type: yes/0 |
| Extra: 01735a983ebc857eb3dac7f7b3aa9db81489a8380b8e509cd8f439079c22db375402090000000793369e7d00 | ||
1 output(s) for total of 35.146207822163 HMNY
| stealth address | amount | amount idx | tag |
| 00: 652cedef61fcc80dc729e17cf06ea1397810b6c6539daa99113417b24ced4db5 | 35.146207822163 | 580 of 0 | <79> |
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": 630,
"vin": [ {
"gen": {
"height": 570
}
}
],
"vout": [ {
"amount": 35146207822163,
"target": {
"tagged_key": {
"key": "652cedef61fcc80dc729e17cf06ea1397810b6c6539daa99113417b24ced4db5",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 115, 90, 152, 62, 188, 133, 126, 179, 218, 199, 247, 179, 170, 157, 184, 20, 137, 168, 56, 11, 142, 80, 156, 216, 244, 57, 7, 156, 34, 219, 55, 84, 2, 9, 0, 0, 0, 7, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}