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: 38521fd81e0b03bf59e3b67832a0bf4be78aa48db29814eb532532976d89c99c
Tx prefix hash: 8bb6ad67a0dbb980ec0fcab51f8e6cde7d8a41532e7718bce7528763e6be0c0a
Tx public key: f8bd333d214c0d4a2bccff1edf44d22484ac127ace0182eb81bbe7fea70d3126
| Timestamp: 1780686158 | Timestamp [UTC]: 2026-06-05 19:02:38 | Age [y:d:h:m:s]: 00:003:05:44:09 |
| Block: 5414 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2472 | RingCT/type: yes/0 |
| Extra: 01f8bd333d214c0d4a2bccff1edf44d22484ac127ace0182eb81bbe7fea70d3126020900000002e49593ff00 | ||
1 output(s) for total of 34.822980264665 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8e8ca8a8a1c7ab0559e689a1025937b542738fe13a09b706f0aed94077908c2f | 34.822980264665 | 6851 of 0 | <4e> |
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": 5474,
"vin": [ {
"gen": {
"height": 5414
}
}
],
"vout": [ {
"amount": 34822980264665,
"target": {
"tagged_key": {
"key": "8e8ca8a8a1c7ab0559e689a1025937b542738fe13a09b706f0aed94077908c2f",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 248, 189, 51, 61, 33, 76, 13, 74, 43, 204, 255, 30, 223, 68, 210, 36, 132, 172, 18, 122, 206, 1, 130, 235, 129, 187, 231, 254, 167, 13, 49, 38, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}