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: d27e9003b76a9f91188d3f66d902449158550c722fc9515d00cfc3c05fe46fea
Tx prefix hash: 607a171750be357a4872af914c22256fd9151cd5dc7d9534b6566a32acb09fea
Tx public key: f6e9476b32e1e6a10ea5bd49cd32b8113250c0ca6d847b3bee1b193e3b337d30
| Timestamp: 1779953684 | Timestamp [UTC]: 2026-05-28 07:34:44 | Age [y:d:h:m:s]: 00:011:19:15:04 |
| Block: 3655 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4244 | RingCT/type: yes/0 |
| Extra: 01f6e9476b32e1e6a10ea5bd49cd32b8113250c0ca6d847b3bee1b193e3b337d3002090000000426697be300 | ||
1 output(s) for total of 34.940008595779 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6bccce3f6a3ddcbf9ae47af0b6732bb1414e8d5d45a09c3640c1079c9bbc9ea4 | 34.940008595779 | 4417 of 0 | <fc> |
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": 3715,
"vin": [ {
"gen": {
"height": 3655
}
}
],
"vout": [ {
"amount": 34940008595779,
"target": {
"tagged_key": {
"key": "6bccce3f6a3ddcbf9ae47af0b6732bb1414e8d5d45a09c3640c1079c9bbc9ea4",
"view_tag": "fc"
}
}
}
],
"extra": [ 1, 246, 233, 71, 107, 50, 225, 230, 161, 14, 165, 189, 73, 205, 50, 184, 17, 50, 80, 192, 202, 109, 132, 123, 59, 238, 27, 25, 62, 59, 51, 125, 48, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}