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: fe1bbc8f485381c343b8294a799fb5f4d7512f37079ddaf2dc7e14ee7fabb8e9
Tx prefix hash: d568ee58ba66311cc2c1de956e5c931a00915beb3b942251fa8f876c71af3afb
Tx public key: b1a8afa13609a87366f50d8e17f6dd6d8e030f8d7ee51f7f597605447e533d56
| Timestamp: 1779927413 | Timestamp [UTC]: 2026-05-28 00:16:53 | Age [y:d:h:m:s]: 00:012:04:16:09 |
| Block: 3383 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4642 | RingCT/type: yes/0 |
| Extra: 01b1a8afa13609a87366f50d8e17f6dd6d8e030f8d7ee51f7f597605447e533d5602090000000126697be300 | ||
1 output(s) for total of 34.958140151493 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2aee2b8a8205bd230c18793591caaa85cda465701ca842dc18342d2a7db285d2 | 34.958140151493 | 4086 of 0 | <e9> |
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": 3443,
"vin": [ {
"gen": {
"height": 3383
}
}
],
"vout": [ {
"amount": 34958140151493,
"target": {
"tagged_key": {
"key": "2aee2b8a8205bd230c18793591caaa85cda465701ca842dc18342d2a7db285d2",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 177, 168, 175, 161, 54, 9, 168, 115, 102, 245, 13, 142, 23, 246, 221, 109, 142, 3, 15, 141, 126, 229, 31, 127, 89, 118, 5, 68, 126, 83, 61, 86, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}