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: 3ed59cc423b5e7faf1fc66d7fed8b61542d95e4b8a135b6b50bb63dcc08797af
Tx prefix hash: 1fe8e6d7009cde3e546af8f6e3771a13064e9d4121fed64cae8dd9406d0bf6cb
Tx public key: c6310c81c65e2422960f9ad533f304ec26f5922c13048b2e522f721861ad1c49
| Timestamp: 1779508710 | Timestamp [UTC]: 2026-05-23 03:58:30 | Age [y:d:h:m:s]: 00:021:07:03:46 |
| Block: 673 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8072 | RingCT/type: yes/0 |
| Extra: 01c6310c81c65e2422960f9ad533f304ec26f5922c13048b2e522f721861ad1c49020900000003ba6d17be00 | ||
1 output(s) for total of 35.141904178416 HMNY
| stealth address | amount | amount idx | tag |
| 00: e11a4da278c221863d1b4c22665824fb894fdf4edde01eb6b212b22051c3676e | 35.141904178416 | 736 of 0 | <ce> |
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": 733,
"vin": [ {
"gen": {
"height": 673
}
}
],
"vout": [ {
"amount": 35141904178416,
"target": {
"tagged_key": {
"key": "e11a4da278c221863d1b4c22665824fb894fdf4edde01eb6b212b22051c3676e",
"view_tag": "ce"
}
}
}
],
"extra": [ 1, 198, 49, 12, 129, 198, 94, 36, 34, 150, 15, 154, 213, 51, 243, 4, 236, 38, 245, 146, 44, 19, 4, 139, 46, 82, 47, 114, 24, 97, 173, 28, 73, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}