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: 1706ac727dc7313813140c5318e0e715b5cec7e94fddaea51565a0c0f099d0de
Tx prefix hash: 9ee06313a42bfb8be5f10863d2b2b58e0dfd056571eaa27801d5ffeca11435de
Tx public key: d784b06c99e46a6436a5b5f367a056e9544920a7c58d4653707ec3abeedfac12
| Timestamp: 1780761601 | Timestamp [UTC]: 2026-06-06 16:00:01 | Age [y:d:h:m:s]: 00:002:11:50:57 |
| Block: 6574 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1392 | RingCT/type: yes/0 |
| Extra: 01d784b06c99e46a6436a5b5f367a056e9544920a7c58d4653707ec3abeedfac12020900000002e49593ff00 | ||
1 output(s) for total of 34.752645068363 HMNY
| stealth address | amount | amount idx | tag |
| 00: 36adcda1c3dfdafd9506a0cbe90bb085af3521173888b8df4a30dbbef4bf013b | 34.752645068363 | 8096 of 0 | <ee> |
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": 6634,
"vin": [ {
"gen": {
"height": 6574
}
}
],
"vout": [ {
"amount": 34752645068363,
"target": {
"tagged_key": {
"key": "36adcda1c3dfdafd9506a0cbe90bb085af3521173888b8df4a30dbbef4bf013b",
"view_tag": "ee"
}
}
}
],
"extra": [ 1, 215, 132, 176, 108, 153, 228, 106, 100, 54, 165, 181, 243, 103, 160, 86, 233, 84, 73, 32, 167, 197, 141, 70, 83, 112, 126, 195, 171, 238, 223, 172, 18, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}