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: 4f9d0b0320d8f689547349f5a7a5c0591f014bc8777af3d55c74597bff029ac9
Tx prefix hash: 9a51329ba6a225bb099e9bd89b236b711bb1cb09f34906e4b6c035eab545ad3f
Tx public key: afbecf824645dde93a26ad92f9641ccbb082a1a3fd4b8d09031672c0504a5a5f
| Timestamp: 1780064254 | Timestamp [UTC]: 2026-05-29 14:17:34 | Age [y:d:h:m:s]: 00:010:12:32:14 |
| Block: 4561 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3360 | RingCT/type: yes/0 |
| Extra: 01afbecf824645dde93a26ad92f9641ccbb082a1a3fd4b8d09031672c0504a5a5f02090000000126697be300 | ||
1 output(s) for total of 34.879682320378 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0be661be3f0b79f5874a173bd0648dfd7f5b7bc6a735023d021e5a1b9ecd5d1b | 34.879682320378 | 5725 of 0 | <e2> |
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": 4621,
"vin": [ {
"gen": {
"height": 4561
}
}
],
"vout": [ {
"amount": 34879682320378,
"target": {
"tagged_key": {
"key": "0be661be3f0b79f5874a173bd0648dfd7f5b7bc6a735023d021e5a1b9ecd5d1b",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 175, 190, 207, 130, 70, 69, 221, 233, 58, 38, 173, 146, 249, 100, 28, 203, 176, 130, 161, 163, 253, 75, 141, 9, 3, 22, 114, 192, 80, 74, 90, 95, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}