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: 0e4b82bda5274224d780c2e1cce71a938690a7012091ee955903d7ce064f35e4
Tx prefix hash: 087fd69e431295e98c957a4d95feb058be278c50dac7964479534fc1df1b708a
Tx public key: df80fe1d929eebd294b6bf8cd97b6c92b50d25386dab87c1b976baf187d4feb9
| Timestamp: 1780994608 | Timestamp [UTC]: 2026-06-09 08:43:28 | Age [y:d:h:m:s]: 00:007:23:52:46 |
| Block: 8302 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 443 | RingCT/type: yes/0 |
| Extra: 01df80fe1d929eebd294b6bf8cd97b6c92b50d25386dab87c1b976baf187d4feb9020900000001e49593ff00 | ||
1 output(s) for total of 34.631687725776 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2117be0439a242512eb133fe97d26f6e66ed61d7ee70180becd4951dbb0aae38 | 34.631687725776 | 10272 of 0 | <e4> |
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": 8362,
"vin": [ {
"gen": {
"height": 8302
}
}
],
"vout": [ {
"amount": 34631687725776,
"target": {
"tagged_key": {
"key": "2117be0439a242512eb133fe97d26f6e66ed61d7ee70180becd4951dbb0aae38",
"view_tag": "e4"
}
}
}
],
"extra": [ 1, 223, 128, 254, 29, 146, 158, 235, 210, 148, 182, 191, 140, 217, 123, 108, 146, 181, 13, 37, 56, 109, 171, 135, 193, 185, 118, 186, 241, 135, 212, 254, 185, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}