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: 5757afdfdf298b306007cc0b54ebea7e45d1d1bb30ebcfa8e1f95a583f693541
Tx prefix hash: b8e57e750a0154471e5b4954bad6d72d782b58d15bdf18d95d23747aaa3391bf
Tx public key: aac64f664eb5f6c01f46003a3954bac8147f384123c53ab2ea5084367e7efdd3
| Timestamp: 1780994385 | Timestamp [UTC]: 2026-06-09 08:39:45 | Age [y:d:h:m:s]: 00:000:08:12:11 |
| Block: 8299 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 424 | RingCT/type: yes/0 |
| Extra: 01aac64f664eb5f6c01f46003a3954bac8147f384123c53ab2ea5084367e7efdd3020900000002e49593ff00 | ||
1 output(s) for total of 34.631885890638 HMNY
| stealth address | amount | amount idx | tag |
| 00: 571c7e4a4469e7e8cbf25c63ad164e6e327e8015ce42ef5da4be33fcdfbcc5a7 | 34.631885890638 | 10269 of 0 | <a5> |
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": 8359,
"vin": [ {
"gen": {
"height": 8299
}
}
],
"vout": [ {
"amount": 34631885890638,
"target": {
"tagged_key": {
"key": "571c7e4a4469e7e8cbf25c63ad164e6e327e8015ce42ef5da4be33fcdfbcc5a7",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 170, 198, 79, 102, 78, 181, 246, 192, 31, 70, 0, 58, 57, 84, 186, 200, 20, 127, 56, 65, 35, 197, 58, 178, 234, 80, 132, 54, 126, 126, 253, 211, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}