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: 013e1743e299e7af4b17ab22f635c38efa1cf5d814008eac5b1abaafc32e0062
Tx prefix hash: d199ef3a509c90d38a9782bca81c02c5a690246fd31827bd1d452f0c06a98192
Tx public key: cc694db249711eee5b756ffbc0a5f385d2bf2b1b086a3598ba8a0c588d7120fa
| Timestamp: 1779849688 | Timestamp [UTC]: 2026-05-27 02:41:28 | Age [y:d:h:m:s]: 00:012:22:54:29 |
| Block: 2512 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5374 | RingCT/type: yes/0 |
| Extra: 01cc694db249711eee5b756ffbc0a5f385d2bf2b1b086a3598ba8a0c588d7120fa02090000000126697be300 | ||
1 output(s) for total of 35.016264455807 HMNY
| stealth address | amount | amount idx | tag |
| 00: 843a49fc6c99f221b9c207df202824e02a8e22f42fe6c6f0be475197502e29c6 | 35.016264455807 | 2956 of 0 | <3d> |
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": 2572,
"vin": [ {
"gen": {
"height": 2512
}
}
],
"vout": [ {
"amount": 35016264455807,
"target": {
"tagged_key": {
"key": "843a49fc6c99f221b9c207df202824e02a8e22f42fe6c6f0be475197502e29c6",
"view_tag": "3d"
}
}
}
],
"extra": [ 1, 204, 105, 77, 178, 73, 113, 30, 238, 91, 117, 111, 251, 192, 165, 243, 133, 210, 191, 43, 27, 8, 106, 53, 152, 186, 138, 12, 88, 141, 113, 32, 250, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}