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: 8480b35becf9fd0726ec5ed3bff8d175183882906b7c34a6fed39a7e2fc2a743
Tx prefix hash: 6e88c39d3f8abd3c52c111805d54c2430b136fe540b8b41664c38515070281af
Tx public key: 211e60fd11ada75d89c44388eb3b8c3e22a6fee66e0acee4853cd7009ca012f4
| Timestamp: 1780071822 | Timestamp [UTC]: 2026-05-29 16:23:42 | Age [y:d:h:m:s]: 00:010:08:23:05 |
| Block: 4649 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3237 | RingCT/type: yes/0 |
| Extra: 01211e60fd11ada75d89c44388eb3b8c3e22a6fee66e0acee4853cd7009ca012f402090000000226697be300 | ||
1 output(s) for total of 34.873828367226 HMNY
| stealth address | amount | amount idx | tag |
| 00: ee544b315444c8c3133e379eefa20d08258110010cd33b6cce6969eaa07dabcb | 34.873828367226 | 5840 of 0 | <69> |
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": 4709,
"vin": [ {
"gen": {
"height": 4649
}
}
],
"vout": [ {
"amount": 34873828367226,
"target": {
"tagged_key": {
"key": "ee544b315444c8c3133e379eefa20d08258110010cd33b6cce6969eaa07dabcb",
"view_tag": "69"
}
}
}
],
"extra": [ 1, 33, 30, 96, 253, 17, 173, 167, 93, 137, 196, 67, 136, 235, 59, 140, 62, 34, 166, 254, 230, 110, 10, 206, 228, 133, 60, 215, 0, 156, 160, 18, 244, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}