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: e109e4ceac15f468dbb4b1642ac86f7150b9dd00ed3e7ab76625803b47f4e401
Tx prefix hash: 8194b081704acbd4636a57b854ac1b26e1ed0b0715a14651c13955e80b6e98d0
Tx public key: 09f6e9eaf21eadd7789359f9fcd8804406cf014a3a50f5d64852f8120bfa31ce
| Timestamp: 1780825796 | Timestamp [UTC]: 2026-06-07 09:49:56 | Age [y:d:h:m:s]: 00:001:14:56:51 |
| Block: 7260 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 626 | RingCT/type: yes/0 |
| Extra: 0109f6e9eaf21eadd7789359f9fcd8804406cf014a3a50f5d64852f8120bfa31ce020900000002e49593ff00 | ||
1 output(s) for total of 34.715208433959 HMNY
| stealth address | amount | amount idx | tag |
| 00: ce56c7f680663d8d12bc50f7ed2f3dbfe9a18888428f35ad91ffd12c6618d9ad | 34.715208433959 | 8938 of 0 | <96> |
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": 7320,
"vin": [ {
"gen": {
"height": 7260
}
}
],
"vout": [ {
"amount": 34715208433959,
"target": {
"tagged_key": {
"key": "ce56c7f680663d8d12bc50f7ed2f3dbfe9a18888428f35ad91ffd12c6618d9ad",
"view_tag": "96"
}
}
}
],
"extra": [ 1, 9, 246, 233, 234, 242, 30, 173, 215, 120, 147, 89, 249, 252, 216, 128, 68, 6, 207, 1, 74, 58, 80, 245, 214, 72, 82, 248, 18, 11, 250, 49, 206, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}