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: 202627772a9ef2bdf37dd80dddb6a8d1ea148ef04376a875d412f51836f43214
Tx prefix hash: 470655bb511f3b0efd08632eaaf04f63ce538967eab03a078a75beca2c14ea0d
Tx public key: 8c1fbf01d68bed8712b770ad1f71fb93252e17c79545d4c24ef7c79fd65baec6
| Timestamp: 1779874160 | Timestamp [UTC]: 2026-05-27 09:29:20 | Age [y:d:h:m:s]: 00:012:15:17:27 |
| Block: 2857 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5029 | RingCT/type: yes/0 |
| Extra: 018c1fbf01d68bed8712b770ad1f71fb93252e17c79545d4c24ef7c79fd65baec602090000000126697be300 | ||
1 output(s) for total of 34.993230076061 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2049ab5a925052839a19050d90f864162fcc7f1063135eab8016b41a29625633 | 34.993230076061 | 3383 of 0 | <c8> |
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": 2917,
"vin": [ {
"gen": {
"height": 2857
}
}
],
"vout": [ {
"amount": 34993230076061,
"target": {
"tagged_key": {
"key": "2049ab5a925052839a19050d90f864162fcc7f1063135eab8016b41a29625633",
"view_tag": "c8"
}
}
}
],
"extra": [ 1, 140, 31, 191, 1, 214, 139, 237, 135, 18, 183, 112, 173, 31, 113, 251, 147, 37, 46, 23, 199, 149, 69, 212, 194, 78, 247, 199, 159, 214, 91, 174, 198, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}