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: ca0a3da14ca0fc9e8745a40e771e539cc7535cc1c0b6e4864869a330a3e5ef08
Tx prefix hash: 194f74553229be7e81f3ab242bdd3e692b679b62a6c17fa718a0357aaa32c86b
Tx public key: 1b2783a3bcd10e86b7b75f7b08c29df361b1ebde4c2a4e9bb802dc91e7f3a62e
| Timestamp: 1779925663 | Timestamp [UTC]: 2026-05-27 23:47:43 | Age [y:d:h:m:s]: 00:011:23:31:10 |
| Block: 3374 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4512 | RingCT/type: yes/0 |
| Extra: 011b2783a3bcd10e86b7b75f7b08c29df361b1ebde4c2a4e9bb802dc91e7f3a62e02090000000126697be300 | ||
1 output(s) for total of 34.961351453464 HMNY
| stealth address | amount | amount idx | tag |
| 00: 02b9119e0642821dd8365ce454a54d30d9fb8372c6abf4ee1cd7e05d164b2d36 | 34.961351453464 | 4069 of 0 | <9e> |
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": 3434,
"vin": [ {
"gen": {
"height": 3374
}
}
],
"vout": [ {
"amount": 34961351453464,
"target": {
"tagged_key": {
"key": "02b9119e0642821dd8365ce454a54d30d9fb8372c6abf4ee1cd7e05d164b2d36",
"view_tag": "9e"
}
}
}
],
"extra": [ 1, 27, 39, 131, 163, 188, 209, 14, 134, 183, 183, 95, 123, 8, 194, 157, 243, 97, 177, 235, 222, 76, 42, 78, 155, 184, 2, 220, 145, 231, 243, 166, 46, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}