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: db61c7f9bab67e19ef6042bfe9a5774332d88b3fa565366dbfd70d25293ceef7
Tx prefix hash: 2b83059d6a5e7b8a60b25f9ba3a53d632aad83b2c9f5671f4a95947c4e492034
Tx public key: 22c7cd17fd32e743b8b2ddf525d1d92f1a0c40811bc8f77d4e84aab1334f2dc4
| Timestamp: 1780323021 | Timestamp [UTC]: 2026-06-01 14:10:21 | Age [y:d:h:m:s]: 00:007:09:08:32 |
| Block: 5042 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2844 | RingCT/type: yes/0 |
| Extra: 0122c7cd17fd32e743b8b2ddf525d1d92f1a0c40811bc8f77d4e84aab1334f2dc402090000002b26697be300 | ||
1 output(s) for total of 34.847697133658 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8121119a658eaa53bbbe2adc3bf45973edf2b57a402ef90a6fb1e426b5f42207 | 34.847697133658 | 6417 of 0 | <17> |
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": 5102,
"vin": [ {
"gen": {
"height": 5042
}
}
],
"vout": [ {
"amount": 34847697133658,
"target": {
"tagged_key": {
"key": "8121119a658eaa53bbbe2adc3bf45973edf2b57a402ef90a6fb1e426b5f42207",
"view_tag": "17"
}
}
}
],
"extra": [ 1, 34, 199, 205, 23, 253, 50, 231, 67, 184, 178, 221, 245, 37, 209, 217, 47, 26, 12, 64, 129, 27, 200, 247, 125, 78, 132, 170, 177, 51, 79, 45, 196, 2, 9, 0, 0, 0, 43, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}