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: d795207c44596242b2608bad703d29e931f8a39300eaf3c021773e791695f6f9
Tx prefix hash: e58224c51c023498fa51ebe07cd7b2dfa4a0d6601a4011d296c6b5a68e876c08
Tx public key: 52341c7f450765664c14475cf7a7722da2b7028aa2d40ff92aa85521bab3e732
| Timestamp: 1779725359 | Timestamp [UTC]: 2026-05-25 16:09:19 | Age [y:d:h:m:s]: 00:014:09:26:38 |
| Block: 1853 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6033 | RingCT/type: yes/0 |
| Extra: 0152341c7f450765664c14475cf7a7722da2b7028aa2d40ff92aa85521bab3e73202090000000aba6d17be00 | ||
1 output(s) for total of 35.060305610320 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f32a4576b1c219b5ca4ce6822cacff4a23f739f2032181e84c01701f86117ac | 35.060305610320 | 2049 of 0 | <7c> |
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": 1913,
"vin": [ {
"gen": {
"height": 1853
}
}
],
"vout": [ {
"amount": 35060305610320,
"target": {
"tagged_key": {
"key": "8f32a4576b1c219b5ca4ce6822cacff4a23f739f2032181e84c01701f86117ac",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 82, 52, 28, 127, 69, 7, 101, 102, 76, 20, 71, 92, 247, 167, 114, 45, 162, 183, 2, 138, 162, 212, 15, 249, 42, 168, 85, 33, 186, 179, 231, 50, 2, 9, 0, 0, 0, 10, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}