For the Mint section, the relevant Payload Functions to consider are as follows:

• '0x6547d9f1d481fdc21cd38c730c07974f2f61adb7063e76f9d9522ab91f090dac::candymachine::mint_script'
• '0x25d440284ca6c13afadb0e83ff1bccacbaa75175551111d8b7cb5d2854e708f0::candymachine::mint_script'
• '0xc72952110d38e26a3b5308558460c577f3793f9647699cd5b1dae08ee79698a5::candymachine::mint_script'
• '0xe5968b1c8966a2d2eaf10db480fc65d69a0f16935ec9810bc52ec14d893a62c::candymachine::mint_script'
• '0xe743f11e73711a90bc76d5ed3df5a6d979a06b2fce194d8b0ca8faf697f4f5f4::candymachine::mint_script'
• '0x6547d9f1d481fdc21cd38c730c07974f2f61adb7063e76f9d9522ab91f090dac::candymachine::mint_script_many'
• '0xf5be2c27aba7c90943ba5ca5d15571b756a564337e8ae78f6a64264123a02ebb::candymachine::mint_from_merkle'
• '0xc72952110d38e26a3b5308558460c577f3793f9647699cd5b1dae08ee79698a5::candymachine::mint_script_many'
• '0x25d440284ca6c13afadb0e83ff1bccacbaa75175551111d8b7cb5d2854e708f0::candymachine::mint_from_merkle'
• '0x6547d9f1d481fdc21cd38c730c07974f2f61adb7063e76f9d9522ab91f090dac::candymachine::mint_from_merkle_many'
• '0x6547d9f1d481fdc21cd38c730c07974f2f61adb7063e76f9d9522ab91f090dac::candymachine::mint_from_merkle'
• '0xf5be2c27aba7c90943ba5ca5d15571b756a564337e8ae78f6a64264123a02ebb::candymachine::mint_script'
• '0xe5968b1c8966a2d2eaf10db480fc65d69a0f16935ec9810bc52ec14d893a62c::candymachine::mint_script_many'
• '0xf5be2c27aba7c90943ba5ca5d15571b756a564337e8ae78f6a64264123a02ebb::candymachine::mint_from_merkle_many'
• '0xf5be2c27aba7c90943ba5ca5d15571b756a564337e8ae78f6a64264123a02ebb::candymachine::mint_script_many'

It's essential to note that for the collection name, nft_id, and description of each NFT, the information should be extracted from the "fact_transactions" table in the "changes" column, with the condition: f.value:data:data:collection is not null.

To obtain this information, a dedicated section called "main" has been created.

In the "mint_transfers" step, the price needs to be calculated. It's important to consider that transactions labeled with "payload many" may involve multiple mints. In such cases, the price should be divided by the number of records. It's crucial to mention that, for all mint transactions, even with multiple records, calculating the price for each transaction can be accomplished by including one of the transfers (excluding the address 0x305d730682a5311fbfc729a51b8eec73924b40849bff25cf9fdb4348cc0a719a, which represents the transaction address).

To ensure accurate calculation, only one required record (based on the condition qualify row_number() over (partition by tx_hash order by amount desc) = 1) should be selected for each transaction in the next step. Additionally, transactions might have been minted with different tokens, so selecting "mint_token_address" as one of the main columns is necessary. The row_number() condition is applied to obtain "mint_token_address."

In the final step, the previous two sections need to be merged. To calculate the fee amount, the fee address (0x305d730682a5311fbfc729a51b8eec73924b40849bff25cf9fdb4348cc0a719a) should be added and divided by the number of records of that transaction, ensuring correct calculation of the platform fee for each record. Establishing a relationship between these sections facilitates obtaining the desired information. It's worth noting that, to calculate the fee, "token_address" must be '0x1::aptos_coin::aptosCoin.'

Considering that the information in the "prices" table might be incomplete, a left join is implemented to return a null value if no data is found.

I have also developed a dashboard where you can view the code for the Sales sector of the Wapal Marketplace.

Another Dashboard Link:

https://flipsidecrypto.xyz/Afonso_Diaz/source-code-for-wapal-nft-marketplace-ja8duT