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: 6312d567075cc8085b0cac263b2b1860a225ed17ee6832f2ed12c116543c7f48
Tx prefix hash: fa35bddbcebd527ff2d9ff9d9f350517e89c8ae91c14d8e268a97dbcb25fd830
Tx public key: 07e207b93a9c7009a03a388795f8e41b64fcc729b20dbecb6993f161ed5e5ae3
| Timestamp: 1779798869 | Timestamp [UTC]: 2026-05-26 12:34:29 | Age [y:d:h:m:s]: 00:013:12:12:18 |
| Block: 2286 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5600 | RingCT/type: yes/0 |
| Extra: 0107e207b93a9c7009a03a388795f8e41b64fcc729b20dbecb6993f161ed5e5ae302090000000226697be300 | ||
1 output(s) for total of 35.031361862576 HMNY
| stealth address | amount | amount idx | tag |
| 00: 226071fb6574b7a859e281a94522b21644841f38e82def4e0dd5107cc1d7a675 | 35.031361862576 | 2664 of 0 | <62> |
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": 2346,
"vin": [ {
"gen": {
"height": 2286
}
}
],
"vout": [ {
"amount": 35031361862576,
"target": {
"tagged_key": {
"key": "226071fb6574b7a859e281a94522b21644841f38e82def4e0dd5107cc1d7a675",
"view_tag": "62"
}
}
}
],
"extra": [ 1, 7, 226, 7, 185, 58, 156, 112, 9, 160, 58, 56, 135, 149, 248, 228, 27, 100, 252, 199, 41, 178, 13, 190, 203, 105, 147, 241, 97, 237, 94, 90, 227, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}