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: 19fb5cbc03928a7386821f9877df7021e88be589cc3bc44e4ab5e5939b4f89b4
Tx prefix hash: d2c9f858eaeab28ceb476aa46f2cca5eb518d324b0ef738f223314efb1f3534c
Tx public key: 0adc5707e924273952ffda0a9a24cd4bca1baa05047ae8503c5666e1a9ca5a73
| Timestamp: 1779781474 | Timestamp [UTC]: 2026-05-26 07:44:34 | Age [y:d:h:m:s]: 00:013:19:54:16 |
| Block: 2111 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5836 | RingCT/type: yes/0 |
| Extra: 010adc5707e924273952ffda0a9a24cd4bca1baa05047ae8503c5666e1a9ca5a7302090000000126697be300 | ||
1 output(s) for total of 35.043056803951 HMNY
| stealth address | amount | amount idx | tag |
| 00: 478784e681f870debd8fdb3f506bd2a68328ec7451011662869b353fa78ded52 | 35.043056803951 | 2431 of 0 | <e4> |
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": 2171,
"vin": [ {
"gen": {
"height": 2111
}
}
],
"vout": [ {
"amount": 35043056803951,
"target": {
"tagged_key": {
"key": "478784e681f870debd8fdb3f506bd2a68328ec7451011662869b353fa78ded52",
"view_tag": "e4"
}
}
}
],
"extra": [ 1, 10, 220, 87, 7, 233, 36, 39, 57, 82, 255, 218, 10, 154, 36, 205, 75, 202, 27, 170, 5, 4, 122, 232, 80, 60, 86, 102, 225, 169, 202, 90, 115, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}