To start parsing transaction, you need to first initialize TxParser:

There are 2 fields to pass in to initialized TxParser:

1. serializer: The serializer instance that will be used for parsing transaction
2. fetcher (optional): TxParser requires all input UTxO information provided since the transaction CBOR hex only preserves transaction hash and output index. When you are not providing all input UTxO information, the fetcher instance is used to fetch the missing UTxO

After performing the tests, you can interpret the results of the tests using the success and errors methods.

1. success: Return a boolean indicating if all tests are passed
2. errors: Show all the errors that occurred during the tests . If there are no errors, it will return an empty string.

Testing inputs starts with locating the inputs you want to test. The filtering will not reset until the filtering methods are called again.

There are multiple methods available to filter the inputs:

1. allInputs: not apply filters
2. inputsAt: filtering inputs with address
3. inputsWith: filtering inputs with token
4. inputsWithPolicy: filtering inputs with policy id
5. inputsAtWith: filtering inputs with address and token
6. inputsAtWithPolicy: filtering inputs with address and policy id

After applying filters, you can proceed with checking value:

1. inputsValue: Check the total value of the filtered inputs

Testing outputs starts with locating the outputs you want to test. The filtering will not reset until the filtering methods are called again.

There are multiple methods available to filter the outputs:

1. allOutputs: not apply filters
2. outputsAt: filtering outputs with address
3. outputsWith: filtering outputs with token
4. outputsWithPolicy: filtering outputs with policy id
5. outputsAtWith: filtering outputs with address and token
6. outputsAtWithPolicy: filtering outputs with address and policy id

After applying filters, you can proceed with checking value:

1. outputsValue: Check the total value of the filtered outputs
2. outputsInlineDatumExist: Check whether any one of the outputs contains inline datum (provided as CBOR)

Testing mints with below APIs:

1. tokenMinted: Checks if a specific token is minted in the transaction.
2. onlyTokenMinted: Checks if a specific token is minted in the transaction and that it is the only mint.
3. policyOnlyMintedToken: Checks if a specific token is minted in the transaction, ensuring that it is the only mint for the given policy ID.
4. checkPolicyOnlyBurn: Checks if a specific policy ID is burned in the transaction, ensuring that it is the only minting (i.e. burning item).

Testing time with below APIs:

1. validAfter: Checks if the transaction is valid after a specified timestamp.
2. validBefore: Checks if the transaction is valid before a specified timestamp.

Testing time with below APIs:

1. keySigned: Checks if a specific key is signed in the transaction.
2. oneOfKeysSigned: Checks if any one of the specified keys is signed in the transaction.
3. allKeysSigned: Checks if all specified keys are signed in the transaction.