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: 0da4232b652fa7b7cb8831e918b0f2fbf943430fd7696f0e124f75f1729991d1
Tx prefix hash: c39c0f4c330575a666e9dd801af60b21c3192c1b04a9679710ea20fc8575a8ed
Tx public key: 05a2cc56bfacdffdb5e6dc62ba9597077bf9b487c37a989c3d9598338a7e9b4c
| Timestamp: 1780989373 | Timestamp [UTC]: 2026-06-09 07:16:13 | Age [y:d:h:m:s]: 00:000:08:43:31 |
| Block: 8196 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 495 | RingCT/type: yes/0 |
| Extra: 0105a2cc56bfacdffdb5e6dc62ba9597077bf9b487c37a989c3d9598338a7e9b4c020900000002e49593ff00 | ||
1 output(s) for total of 34.638690238747 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8ea05c97cc6328069eeae4ee378f241fed53b1b72af9efd882e3c3e9bea3aa17 | 34.638690238747 | 10148 of 0 | <b3> |
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": 8256,
"vin": [ {
"gen": {
"height": 8196
}
}
],
"vout": [ {
"amount": 34638690238747,
"target": {
"tagged_key": {
"key": "8ea05c97cc6328069eeae4ee378f241fed53b1b72af9efd882e3c3e9bea3aa17",
"view_tag": "b3"
}
}
}
],
"extra": [ 1, 5, 162, 204, 86, 191, 172, 223, 253, 181, 230, 220, 98, 186, 149, 151, 7, 123, 249, 180, 135, 195, 122, 152, 156, 61, 149, 152, 51, 138, 126, 155, 76, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}