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: 6adf7d87bc31bf9158ca1c936eb861f91394b1f48aff7ab591ac431c9141d5a9
Tx prefix hash: 00beff8e1be1d039182a7e8feb7109ef580d240a6eb6a8766dc9b682f7ac9ca3
Tx public key: c1b4333240201ec214ec8e17f3002b687d5d78726f24b310e3ff1196c6407ee8
| Timestamp: 1780734146 | Timestamp [UTC]: 2026-06-06 08:22:26 | Age [y:d:h:m:s]: 00:002:16:24:21 |
| Block: 6346 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1540 | RingCT/type: yes/0 |
| Extra: 01c1b4333240201ec214ec8e17f3002b687d5d78726f24b310e3ff1196c6407ee8020900000001e49593ff00 | ||
1 output(s) for total of 34.761132160616 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3c47031da49f719170f557c5b306d99760ed7fd0517eeb5a03a7f6f67262b180 | 34.761132160616 | 7833 of 0 | <b5> |
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": 6406,
"vin": [ {
"gen": {
"height": 6346
}
}
],
"vout": [ {
"amount": 34761132160616,
"target": {
"tagged_key": {
"key": "3c47031da49f719170f557c5b306d99760ed7fd0517eeb5a03a7f6f67262b180",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 193, 180, 51, 50, 64, 32, 30, 194, 20, 236, 142, 23, 243, 0, 43, 104, 125, 93, 120, 114, 111, 36, 179, 16, 227, 255, 17, 150, 198, 64, 126, 232, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}