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: 70ae3637f38ce773ddadbe4d51fa009a76ec5c4ec9d5521f67978c6de289cdf1
Tx prefix hash: dbcb80be8a1e45d695d703a4ee02bd8fe500ddf6ef5ec714682f7ef443c397c9
Tx public key: c1f7b7c40b811ff2ad259ecbce4dc22f6555997c29486a0d888d2c9954588706
| Timestamp: 1779854503 | Timestamp [UTC]: 2026-05-27 04:01:43 | Age [y:d:h:m:s]: 00:012:20:45:04 |
| Block: 2594 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5292 | RingCT/type: yes/0 |
| Extra: 01c1f7b7c40b811ff2ad259ecbce4dc22f6555997c29486a0d888d2c995458870602090000000126697be300 | ||
1 output(s) for total of 35.010788244463 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0ca1a59ec099583eb5cd6e7605609c18d8272ee5be35aed2d638d4194bd75d92 | 35.010788244463 | 3054 of 0 | <2d> |
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": 2654,
"vin": [ {
"gen": {
"height": 2594
}
}
],
"vout": [ {
"amount": 35010788244463,
"target": {
"tagged_key": {
"key": "0ca1a59ec099583eb5cd6e7605609c18d8272ee5be35aed2d638d4194bd75d92",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 193, 247, 183, 196, 11, 129, 31, 242, 173, 37, 158, 203, 206, 77, 194, 47, 101, 85, 153, 124, 41, 72, 106, 13, 136, 141, 44, 153, 84, 88, 135, 6, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}