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: 135f919ca124a830c103f3c4e139d684bab92e4abdc68d806ac5e64533ad4a44
Tx prefix hash: cbc5118e4873c6614920a53019ea6e7877d34133a1b6da23d2e03504dfb3fb2e
Tx public key: 68095d696e5394dead9b309a1e4cbf3085d30f508a5635a1de3ff63f8b268ff1
| Timestamp: 1779782362 | Timestamp [UTC]: 2026-05-26 07:59:22 | Age [y:d:h:m:s]: 00:013:17:36:35 |
| Block: 2124 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5762 | RingCT/type: yes/0 |
| Extra: 0168095d696e5394dead9b309a1e4cbf3085d30f508a5635a1de3ff63f8b268ff102090000000126697be300 | ||
1 output(s) for total of 35.042187902651 HMNY
| stealth address | amount | amount idx | tag |
| 00: 38db68fc4d31652be587bf7b4228b43a704b09497a037b8be580fbbe38c3d948 | 35.042187902651 | 2448 of 0 | <fe> |
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": 2184,
"vin": [ {
"gen": {
"height": 2124
}
}
],
"vout": [ {
"amount": 35042187902651,
"target": {
"tagged_key": {
"key": "38db68fc4d31652be587bf7b4228b43a704b09497a037b8be580fbbe38c3d948",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 104, 9, 93, 105, 110, 83, 148, 222, 173, 155, 48, 154, 30, 76, 191, 48, 133, 211, 15, 80, 138, 86, 53, 161, 222, 63, 246, 63, 139, 38, 143, 241, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}