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: 69e9a0c8928e1ad9771b84355c11d7ca036c383c0ed9a5a4451021af2bc1e720
Tx prefix hash: 47f4a00cebdcf4a2a1be88b9227bd11c1a518ae408af6c7e8c88669401947cf6
Tx public key: 1ae8a2640ca1d29c2f7115fbbf124f75699b62d3c7a49f16b5aec3c2d5689cbc
| Timestamp: 1780819939 | Timestamp [UTC]: 2026-06-07 08:12:19 | Age [y:d:h:m:s]: 00:001:15:06:34 |
| Block: 7149 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 737 | RingCT/type: yes/0 |
| Extra: 011ae8a2640ca1d29c2f7115fbbf124f75699b62d3c7a49f16b5aec3c2d5689cbc020900000001e49593ff00 | ||
1 output(s) for total of 34.707932677356 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f6ae5924ae419a46c1c7b14bd627d26ca014f25c6f661e8dc42b5b661b22254 | 34.707932677356 | 8809 of 0 | <37> |
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": 7209,
"vin": [ {
"gen": {
"height": 7149
}
}
],
"vout": [ {
"amount": 34707932677356,
"target": {
"tagged_key": {
"key": "0f6ae5924ae419a46c1c7b14bd627d26ca014f25c6f661e8dc42b5b661b22254",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 26, 232, 162, 100, 12, 161, 210, 156, 47, 113, 21, 251, 191, 18, 79, 117, 105, 155, 98, 211, 199, 164, 159, 22, 181, 174, 195, 194, 213, 104, 156, 188, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}