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: cd23c4ac5dc41e56b1c11cb04c429db3e4df866e3a338b612cb78dcc0ea07608
Tx prefix hash: aad41db99cae2bdf5337d85c92e1e788e964f1ec06e75a10c7f4f0941b264dfe
Tx public key: ee78d1972ea054ecbbae3b1a100c6bd9a8c2c35d91be5329024519eb7128e833
| Timestamp: 1779960546 | Timestamp [UTC]: 2026-05-28 09:29:06 | Age [y:d:h:m:s]: 00:011:17:11:30 |
| Block: 3752 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4144 | RingCT/type: yes/0 |
| Extra: 01ee78d1972ea054ecbbae3b1a100c6bd9a8c2c35d91be5329024519eb7128e83302090000000326697be300 | ||
1 output(s) for total of 34.933544838143 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0700437a258ec03f3add8d6a24b6e6e728bc5ce3ce6d98e1690385ad5462c0bf | 34.933544838143 | 4550 of 0 | <7c> |
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": 3812,
"vin": [ {
"gen": {
"height": 3752
}
}
],
"vout": [ {
"amount": 34933544838143,
"target": {
"tagged_key": {
"key": "0700437a258ec03f3add8d6a24b6e6e728bc5ce3ce6d98e1690385ad5462c0bf",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 238, 120, 209, 151, 46, 160, 84, 236, 187, 174, 59, 26, 16, 12, 107, 217, 168, 194, 195, 93, 145, 190, 83, 41, 2, 69, 25, 235, 113, 40, 232, 51, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}