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: 16cb3a77d2ed6b70a7a5ce0fada6cffac6ca2ef25281e3ba2e145216b0f82ae2
Tx prefix hash: a4daed4fef3d54b39d9c2b08080a1a21c14c9df65c7efa2e96d2cfbace0ebab3
Tx public key: ee465ac20c0c2917f3e1fbd2cbf2133e3df7c825a8193b2eb5aa2ac4fe56f28f
| Timestamp: 1779951126 | Timestamp [UTC]: 2026-05-28 06:52:06 | Age [y:d:h:m:s]: 00:020:01:30:13 |
| Block: 3626 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5119 | RingCT/type: yes/0 |
| Extra: 01ee465ac20c0c2917f3e1fbd2cbf2133e3df7c825a8193b2eb5aa2ac4fe56f28f02090000000226697be300 | ||
1 output(s) for total of 34.941941291625 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1294fb971bafcaa752b69fc703ac167eabf18ec2ab9da93b1251986c0dcc45ec | 34.941941291625 | 4379 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": 3686,
"vin": [ {
"gen": {
"height": 3626
}
}
],
"vout": [ {
"amount": 34941941291625,
"target": {
"tagged_key": {
"key": "1294fb971bafcaa752b69fc703ac167eabf18ec2ab9da93b1251986c0dcc45ec",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 238, 70, 90, 194, 12, 12, 41, 23, 243, 225, 251, 210, 203, 242, 19, 62, 61, 247, 200, 37, 168, 25, 59, 46, 181, 170, 42, 196, 254, 86, 242, 143, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}