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: afa8f422223f06697a3af693d06026f25a8d552f4e52930ef0c93ee11c645079
Tx prefix hash: 2bb458cbbc97ae106be56ef9c719a7cad447b847535194caf13bfb84e5719fcf
Tx public key: 0cc13cd9e451b263add47ed28081c68f10123179f66fb24d902cda8504126b32
| Timestamp: 1779790258 | Timestamp [UTC]: 2026-05-26 10:10:58 | Age [y:d:h:m:s]: 00:013:17:27:52 |
| Block: 2214 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5731 | RingCT/type: yes/0 |
| Extra: 010cc13cd9e451b263add47ed28081c68f10123179f66fb24d902cda8504126b3202090000000126697be300 | ||
1 output(s) for total of 35.036173022964 HMNY
| stealth address | amount | amount idx | tag |
| 00: 192f911a84b56f4f2a2b50734c6015c940c1d2bd560c678410acb7a31fdaae7c | 35.036173022964 | 2564 of 0 | <b0> |
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": 2274,
"vin": [ {
"gen": {
"height": 2214
}
}
],
"vout": [ {
"amount": 35036173022964,
"target": {
"tagged_key": {
"key": "192f911a84b56f4f2a2b50734c6015c940c1d2bd560c678410acb7a31fdaae7c",
"view_tag": "b0"
}
}
}
],
"extra": [ 1, 12, 193, 60, 217, 228, 81, 178, 99, 173, 212, 126, 210, 128, 129, 198, 143, 16, 18, 49, 121, 246, 111, 178, 77, 144, 44, 218, 133, 4, 18, 107, 50, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}