Transaction Hash:
Block:
19501177 at Mar-24-2024 01:33:59 AM +UTC
Transaction Fee:
0.000700781327986413 ETH
$2.38
Gas Used:
47,163 Gas / 14.858709751 Gwei
Emitted Events:
618 |
KATA.Approval( owner=[Sender] 0x82c5c6d83041e34b186582bf10128d66ba93003f, spender=0x881D4023...dC08D300C, value=115792089237316195423570985008687907853269984665640564039457584007913129639935 )
|
Account State Difference:
Address | Before | After | State Difference | ||
---|---|---|---|---|---|
0x2e85ae1C...aA222aE15 | |||||
0x388C818C...7ccB19297
Miner
| (Lido: Execution Layer Rewards Vault) | 71.545095095124455802 Eth | 71.545097211313550946 Eth | 0.000002116189095144 | |
0x82c5C6D8...6ba93003F |
0.617998944350186448 Eth
Nonce: 61
|
0.617298163022200035 Eth
Nonce: 62
| 0.000700781327986413 |
Execution Trace
KATA.approve( spender=0x881D40237659C251811CEC9c364ef91dC08D300C, amount=115792089237316195423570985008687907853269984665640564039457584007913129639935 ) => ( True )
approve[KATA (ln:131)]
_approve[KATA (ln:132)]
Approval[KATA (ln:249)]
1234567891011121314151617181920212223242526// SPDX-License-Identifier: MITpragma solidity ^0.8.0;/*** @dev Implementation of the {IERC20} interface.** This implementation is agnostic to the way tokens are created. This means* that a supply mechanism has to be added in a derived contract using {_mint}.* For a generic mechanism see {ERC20PresetMinterPauser}.** TIP: For a detailed writeup see our guide* https://forum.zeppelin.solutions/t/how-to-implement-erc20-supply-mechanisms/226[How* to implement supply mechanisms].** We have followed general OpenZeppelin Contracts guidelines: functions revert* instead returning `false` on failure. This behavior is nonetheless* conventional and does not conflict with the expectations of ERC20* applications.** Additionally, an {Approval} event is emitted on calls to {transferFrom}.* This allows applications to reconstruct the allowance for all accounts just* by listening to said events. Other implementations of the EIP may not emit* these events, as it isn't required by the specification.** Finally, the non-standard {decreaseAllowance} and {increaseAllowance}* functions have been added to mitigate the well-known issues around setting* allowances. See {IERC20-approve}.