-
Contract A (0x41275dcfcf2a8c3edc94f87da477d38a2ca56390) is created in Block #5470416 and has a balance of 0 Ether.
-
Contract B (0x32fc1ad1de149a3c9e0bf4aff2989f699eaae30f) is created by Contract A in Block #5470419 and within the same transaction the following occurs:
- Contract A calls Contract B with 0.1 Ether.
- Contract B calls itself with 0.1 Ether and in a sub call transfers 0.000000000001193046 Ether to a third address (0x30bc5920a76b483080523482d7fc2b64c9d5bd80)/
- Contract B self destructs, refunding its balance of 0.099999999998806954 Ether to Contract A.
- Contract A calls the now destroyed Contract B with 0.099999999998806954 Ether.
-
Contract A holds a balance of 0 Ether.
The final call from Contract A to Contract B, after Contract B had self destructed, should have failed with the balance of 0.099999999998806954 Ether remaining with Contract A.
It would appear the Ether in the final call from Contract A to Contract B has been 'destroyed', as it was neither assigned to Contract A nor Contract B.
Within this gist you will find some traces taken from Parity and a screenshot of the the scenario described taken from Etherscan.
