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: 6bf798f02a24665c913cb8077a63261e8ed77308a31a3407b1e3a971a4ba2e0e
Tx prefix hash: 4867ce620b970ca7b6c6d7d9a7166a8b784f0aa0c9b475d3af330d98f2c116dd
Tx public key: ebeae6fba473a1c8ad2a48b7f5046d3e15b00d38b3083a9359c446ac4aeee8fb
| Timestamp: 1781012131 | Timestamp [UTC]: 2026-06-09 13:35:31 | Age [y:d:h:m:s]: 00:005:18:44:04 |
| Block: 8596 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 149 | RingCT/type: yes/0 |
| Extra: 01ebeae6fba473a1c8ad2a48b7f5046d3e15b00d38b3083a9359c446ac4aeee8fb020900000001e49593ff00 | ||
1 output(s) for total of 34.612273068798 HMNY
| stealth address | amount | amount idx | tag |
| 00: ee570dc5033f23a749d3d9d25cd4b00cb1cd3d36c3b535d5c47a50d214e097fa | 34.612273068798 | 10622 of 0 | <e1> |
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": 8656,
"vin": [ {
"gen": {
"height": 8596
}
}
],
"vout": [ {
"amount": 34612273068798,
"target": {
"tagged_key": {
"key": "ee570dc5033f23a749d3d9d25cd4b00cb1cd3d36c3b535d5c47a50d214e097fa",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 235, 234, 230, 251, 164, 115, 161, 200, 173, 42, 72, 183, 245, 4, 109, 62, 21, 176, 13, 56, 179, 8, 58, 147, 89, 196, 70, 172, 74, 238, 232, 251, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}