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: 7d42488e9b41aae9a4f98b065e1e596ba30e2eac0bd834d52608801a9e0bd2cc
Tx prefix hash: f9fafa25e8678dbc94b2774ad857f354e5d68aa26be8963f631a2eff6903175a
Tx public key: 2ea8230bf9cdcad997243fa3cb2f9d79d30c712ea8c5dfa798d8eb5d7ca40cc4
| Timestamp: 1780044281 | Timestamp [UTC]: 2026-05-29 08:44:41 | Age [y:d:h:m:s]: 00:010:18:54:09 |
| Block: 4326 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3615 | RingCT/type: yes/0 |
| Extra: 012ea8230bf9cdcad997243fa3cb2f9d79d30c712ea8c5dfa798d8eb5d7ca40cc402090000000126697be300 | ||
1 output(s) for total of 34.895319852492 HMNY
| stealth address | amount | amount idx | tag |
| 00: e2fafb658ef133be92fc3d6c111c996f1c43a4a55db7efdd09f077c7abd8061b | 34.895319852492 | 5406 of 0 | <67> |
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": 4386,
"vin": [ {
"gen": {
"height": 4326
}
}
],
"vout": [ {
"amount": 34895319852492,
"target": {
"tagged_key": {
"key": "e2fafb658ef133be92fc3d6c111c996f1c43a4a55db7efdd09f077c7abd8061b",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 46, 168, 35, 11, 249, 205, 202, 217, 151, 36, 63, 163, 203, 47, 157, 121, 211, 12, 113, 46, 168, 197, 223, 167, 152, 216, 235, 93, 124, 164, 12, 196, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}