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: b48da4f31fe0a6a00bb833535c2ccd7447bfe90f3871d9f9c0096be181d08c13
Tx prefix hash: bdb89280a94a5b0502cc00f3e2cdc9e159a9c5ffc0dfc260394df415fc11fb88
Tx public key: a7ce66d58907cb9a32f61a48fc132ab9dce256a52f37af25006d7a86853fb2bb
| Timestamp: 1780323266 | Timestamp [UTC]: 2026-06-01 14:14:26 | Age [y:d:h:m:s]: 00:007:06:57:41 |
| Block: 5093 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2793 | RingCT/type: yes/0 |
| Extra: 01a7ce66d58907cb9a32f61a48fc132ab9dce256a52f37af25006d7a86853fb2bb02090000003f26697be300 | ||
1 output(s) for total of 34.844307493210 HMNY
| stealth address | amount | amount idx | tag |
| 00: f0fcab491e66c6a3f322a9351128ef28230cf009946ad5f3bd21ad941ab6384f | 34.844307493210 | 6468 of 0 | <6c> |
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": 5153,
"vin": [ {
"gen": {
"height": 5093
}
}
],
"vout": [ {
"amount": 34844307493210,
"target": {
"tagged_key": {
"key": "f0fcab491e66c6a3f322a9351128ef28230cf009946ad5f3bd21ad941ab6384f",
"view_tag": "6c"
}
}
}
],
"extra": [ 1, 167, 206, 102, 213, 137, 7, 203, 154, 50, 246, 26, 72, 252, 19, 42, 185, 220, 226, 86, 165, 47, 55, 175, 37, 0, 109, 122, 134, 133, 63, 178, 187, 2, 9, 0, 0, 0, 63, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}