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: 23d5e4a45ec22d31cc1ebc48b207cd1c6b94a58024cb86ac76ad2c350ffd7188
Tx prefix hash: e06c7a65e41103a4077a74374631173f552794021b4f7cd88482ebe8dbe75cac
Tx public key: 2685f5796dce3eaea6d9895f3b60cdef6459b86d6084a398f0e60e5b9b6cf13d
| Timestamp: 1779721220 | Timestamp [UTC]: 2026-05-25 15:00:20 | Age [y:d:h:m:s]: 00:014:10:35:37 |
| Block: 1758 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6128 | RingCT/type: yes/0 |
| Extra: 012685f5796dce3eaea6d9895f3b60cdef6459b86d6084a398f0e60e5b9b6cf13d020900000005ba6d17be00 | ||
1 output(s) for total of 35.098642653445 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8dbf4cbb367e62dfbf909a29baef37fcdc334bd2e56c4f415eca97c19978e85d | 35.098642653445 | 1938 of 0 | <d6> |
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": 1818,
"vin": [ {
"gen": {
"height": 1758
}
}
],
"vout": [ {
"amount": 35098642653445,
"target": {
"tagged_key": {
"key": "8dbf4cbb367e62dfbf909a29baef37fcdc334bd2e56c4f415eca97c19978e85d",
"view_tag": "d6"
}
}
}
],
"extra": [ 1, 38, 133, 245, 121, 109, 206, 62, 174, 166, 217, 137, 95, 59, 96, 205, 239, 100, 89, 184, 109, 96, 132, 163, 152, 240, 230, 14, 91, 155, 108, 241, 61, 2, 9, 0, 0, 0, 5, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}