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: 1eb4cc196d949264490956d58fc4ca3bd70f970cb2bdfb20877b1c8dcccd5c8c
Tx prefix hash: 90f1d5ca0d5839d066d82125028b63e8858a54d4343b72c62d0681d9e6764626
Tx public key: ac10d48633c6e17d300e82076a46c80baf395062366259a8937898f3a14af824
| Timestamp: 1780689320 | Timestamp [UTC]: 2026-06-05 19:55:20 | Age [y:d:h:m:s]: 00:007:15:06:56 |
| Block: 5584 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3161 | RingCT/type: yes/0 |
| Extra: 01ac10d48633c6e17d300e82076a46c80baf395062366259a8937898f3a14af824020900000001e49593ff00 | ||
1 output(s) for total of 34.811690758458 HMNY
| stealth address | amount | amount idx | tag |
| 00: d1f93869c721f0133c717c21e80a92db72fdee84ff08eba7c7a2842283185983 | 34.811690758458 | 7029 of 0 | <12> |
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": 5644,
"vin": [ {
"gen": {
"height": 5584
}
}
],
"vout": [ {
"amount": 34811690758458,
"target": {
"tagged_key": {
"key": "d1f93869c721f0133c717c21e80a92db72fdee84ff08eba7c7a2842283185983",
"view_tag": "12"
}
}
}
],
"extra": [ 1, 172, 16, 212, 134, 51, 198, 225, 125, 48, 14, 130, 7, 106, 70, 200, 11, 175, 57, 80, 98, 54, 98, 89, 168, 147, 120, 152, 243, 161, 74, 248, 36, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}