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: 77815c24a271398857ae9bec4ae50414896446d04569dad6f2f2796e61858265
Tx prefix hash: e9d3e3fa29a1467e45735325375b56776849d140ea916442a9a5f2942cb10abe
Tx public key: 5b05178958ceadb2bb0799a1b5673a6e8c02db6182c2b7754a6b1c30363fcaf0
| Timestamp: 1780843669 | Timestamp [UTC]: 2026-06-07 14:47:49 | Age [y:d:h:m:s]: 00:001:08:31:04 |
| Block: 7487 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 399 | RingCT/type: yes/0 |
| Extra: 015b05178958ceadb2bb0799a1b5673a6e8c02db6182c2b7754a6b1c30363fcaf0020900000001e49593ff00 | ||
1 output(s) for total of 34.685564223845 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56cdb8d940629b930d995567ff5a62c4ea31d0cfcc2d33f0dbc3ae32ee214c99 | 34.685564223845 | 9225 of 0 | <16> |
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": 7547,
"vin": [ {
"gen": {
"height": 7487
}
}
],
"vout": [ {
"amount": 34685564223845,
"target": {
"tagged_key": {
"key": "56cdb8d940629b930d995567ff5a62c4ea31d0cfcc2d33f0dbc3ae32ee214c99",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 91, 5, 23, 137, 88, 206, 173, 178, 187, 7, 153, 161, 181, 103, 58, 110, 140, 2, 219, 97, 130, 194, 183, 117, 74, 107, 28, 48, 54, 63, 202, 240, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}