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: e66653d02b64b0d07ad5a1790dc3a8821d3a1f55dd960802ae429fd4579389ef
Tx prefix hash: 79f057f675b3c59d0e669a4ce56372523bc8e57bc0ce4ead02e358746141811d
Tx public key: 4aee262a01ed8cb631e6c64a6380ecd81323d9330b30d1dd4ab2fb252e3d0f70
| Timestamp: 1779941651 | Timestamp [UTC]: 2026-05-28 04:14:11 | Age [y:d:h:m:s]: 00:011:20:32:36 |
| Block: 3508 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4378 | RingCT/type: yes/0 |
| Extra: 014aee262a01ed8cb631e6c64a6380ecd81323d9330b30d1dd4ab2fb252e3d0f7002090000000426697be300 | ||
1 output(s) for total of 34.949806466935 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8e70294a56e2b19a76cd6036f06f23842f072c698e2bb45fa33be5588d35ba2f | 34.949806466935 | 4230 of 0 | <df> |
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": 3568,
"vin": [ {
"gen": {
"height": 3508
}
}
],
"vout": [ {
"amount": 34949806466935,
"target": {
"tagged_key": {
"key": "8e70294a56e2b19a76cd6036f06f23842f072c698e2bb45fa33be5588d35ba2f",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 74, 238, 38, 42, 1, 237, 140, 182, 49, 230, 198, 74, 99, 128, 236, 216, 19, 35, 217, 51, 11, 48, 209, 221, 74, 178, 251, 37, 46, 61, 15, 112, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}