When a contract creates a contract, where's the new contract's bytecode stored?

For example:
This Maker contract was created by their deployment contract: <https://etherscan.io/address/0x448a5065aebb8e423f0896e6c5d525c040f59af3>
here's the internal transaction: <https://etherscan.io/txsInternal?block=4752011>

Etherscan says `0x448a5065aebb8e423f0896e6c5d525c040f59af3` was created in transaction `0xa066bef4d74ad5433cc89ea21799d7df3e2f37ec0879f9ca74c419e861064fbf` and normally, when an external transaction creates a contract, that bytecode is in the blockchain in the `input`.

In this case, data was sent to the deployment (existing) contract to tell it to deploy a new contract, but the bytecode for the new contract is not in the blockchain data. Would the bytecode be in the event logs? or somewhere else?