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: 53939c8582665e3b22e0bcc5988fc335fdf6bd097a7a075e1b5d0579f8aa96bb
Tx prefix hash: b55051b71972874eceac53d7abb5d86e918090c0013e3dc67024b17c43e0b1ba
Tx public key: ba696de2d8ae747aa4c4590035b98efc0aaec55eda2532fa1d8e6a09db8b6626
| Timestamp: 1780114780 | Timestamp [UTC]: 2026-05-30 04:19:40 | Age [y:d:h:m:s]: 00:009:21:16:17 |
| Block: 4872 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3014 | RingCT/type: yes/0 |
| Extra: 01ba696de2d8ae747aa4c4590035b98efc0aaec55eda2532fa1d8e6a09db8b662602090000000226697be300 | ||
1 output(s) for total of 34.861617916809 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3c00bbf0504984d59ab5ca07934d6d30c41912a5e6f7d1a1d0690ffcb62680ea | 34.861617916809 | 6156 of 0 | <38> |
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": 4932,
"vin": [ {
"gen": {
"height": 4872
}
}
],
"vout": [ {
"amount": 34861617916809,
"target": {
"tagged_key": {
"key": "3c00bbf0504984d59ab5ca07934d6d30c41912a5e6f7d1a1d0690ffcb62680ea",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 186, 105, 109, 226, 216, 174, 116, 122, 164, 196, 89, 0, 53, 185, 142, 252, 10, 174, 197, 94, 218, 37, 50, 250, 29, 142, 106, 9, 219, 139, 102, 38, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}