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: 8b6ee44178389533119d1b0529b1357eebb04d92cb1b7b540d99dc2755fdf8e9
Tx prefix hash: 4784916f4fc253930fbe2cab4e7a008d2065f1d918fa88a34e65789a19120116
Tx public key: fc7ff69bc1cbd9993b0df7f4755dd219742ce61ae8a5f6d4c1628fc887492f11
| Timestamp: 1779939004 | Timestamp [UTC]: 2026-05-28 03:30:04 | Age [y:d:h:m:s]: 00:011:22:05:53 |
| Block: 3468 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4418 | RingCT/type: yes/0 |
| Extra: 01fc7ff69bc1cbd9993b0df7f4755dd219742ce61ae8a5f6d4c1628fc887492f1102090000000326697be300 | ||
1 output(s) for total of 34.952473029821 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0568f9e784bf70ccc54c50c8123090164daad804bbcf5a3c54adc3041545b0d0 | 34.952473029821 | 4187 of 0 | <09> |
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": 3528,
"vin": [ {
"gen": {
"height": 3468
}
}
],
"vout": [ {
"amount": 34952473029821,
"target": {
"tagged_key": {
"key": "0568f9e784bf70ccc54c50c8123090164daad804bbcf5a3c54adc3041545b0d0",
"view_tag": "09"
}
}
}
],
"extra": [ 1, 252, 127, 246, 155, 193, 203, 217, 153, 59, 13, 247, 244, 117, 93, 210, 25, 116, 44, 230, 26, 232, 165, 246, 212, 193, 98, 143, 200, 135, 73, 47, 17, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}