diff --git a/src/assets/tooling-&-explorers/iexec-explorer/asset-types-advance-filter.png b/src/assets/tooling-&-explorers/iexec-explorer/asset-types-advance-filter.png
new file mode 100644
index 00000000..bee95690
Binary files /dev/null and b/src/assets/tooling-&-explorers/iexec-explorer/asset-types-advance-filter.png differ
diff --git a/src/assets/tooling-&-explorers/iexec-explorer/dataset-view.png b/src/assets/tooling-&-explorers/iexec-explorer/dataset-view.png
index 7d230a0c..096f4e3f 100644
Binary files a/src/assets/tooling-&-explorers/iexec-explorer/dataset-view.png and b/src/assets/tooling-&-explorers/iexec-explorer/dataset-view.png differ
diff --git a/src/assets/tooling-&-explorers/iexec-explorer/task-details-started.png b/src/assets/tooling-&-explorers/iexec-explorer/task-details-started.png
deleted file mode 100644
index a86fe8d7..00000000
Binary files a/src/assets/tooling-&-explorers/iexec-explorer/task-details-started.png and /dev/null differ
diff --git a/src/get-started/tooling-and-explorers/iexec-explorer.md b/src/get-started/tooling-and-explorers/iexec-explorer.md
index 374b33f1..7c32e163 100644
--- a/src/get-started/tooling-and-explorers/iexec-explorer.md
+++ b/src/get-started/tooling-and-explorers/iexec-explorer.md
@@ -114,13 +114,6 @@ Browse and analyze all tasks across the iExec network:
 
 ### Task Execution Monitoring
 
-<ImageViewer
-    :image-url-dark="taskDetailsStartedImage"
-    image-alt="Result Decryption"
-    :link-url="`${explorerUrl}/tasks`"
-    caption="Explore Tasks"
-/>
-
 <ImageViewer
     :image-url-dark="taskDetailsCompletedImage"
     image-alt="Task Completed"
@@ -154,7 +147,7 @@ Browse and analyze all tasks across the iExec network:
   :image-url-dark="appViewImage"
   image-alt="App View"
   :link-url="`${explorerUrl}/apps`"
-  caption="Explore iApp Marketplace"
+  caption="Explore iApp"
 />
 
 Explore the iExec application marketplace:
@@ -169,16 +162,42 @@ Explore the iExec application marketplace:
   :image-url-dark="datasetViewImage"
   image-alt="Dataset View"
   :link-url="`${explorerUrl}/datasets`"
-  caption="Explore Protected Datasets"
+  caption="Explore Protected Data"
 />
 
 Navigate the protected data landscape:
 
-- **Data Catalog**: Discover available datasets with their metadata and asset
-  type
-- **Usage Patterns**: Analyze dataset popularity and user adoption
-- **Schema Validation**: Ensure data structure compatibility with your
-  applications
+- **Data Catalog**: Discover available protected data with their metadata and
+  asset types
+- **Usage Analytics**: Analyze protected data popularity and adoption trends
+  across the network
+- **Schema Discovery**: Find protected data that matches your requirements using
+  advanced filtering
+
+The explorer provides a powerful filtering system that lets you search for
+protected data based on their schema structure, making it easy to find datasets
+compatible with your iApp.
+
+<ImageViewer
+  :image-url-dark="assetTypesAdvanceFilterViewImage"
+  image-alt="asset Types Advance Filter View"
+  :link-url="`${explorerUrl}/datasets`"
+  caption="Explore Asset Types Filter"
+/>
+
+**How to use the asset type filter:**
+
+1. **Select asset type criteria** - Choose from predefined types and enter the
+   field names
+2. **Apply multiple filters** - Combine asset type filters with other criteria
+   like date range, owner, or tags
+3. **Browse matching datasets** - View only the protected data that matches your
+   schema requirements
+
+This filtering capability is essential when building iApps that need specific
+data structures. For example, if your iApp processes user profiles, you can
+filter for datasets containing `email: string` and `age: f64` fields to ensure
+compatibility.
 
 ## Workerpools
 
@@ -186,7 +205,7 @@ Navigate the protected data landscape:
   :image-url-dark="workerpoolViewImage"
   image-alt="Workerpool View"
   :link-url="`${explorerUrl}/workerpools`"
-  caption="Explore Workerpools Infrastructure"
+  caption="Explore Workerpools"
 />
 
 Explore the decentralized computing infrastructure:
@@ -216,9 +235,9 @@ const explorerUrl = computed(() => chainData.value.iexecExplorerUrl);
 import explorerGlobalImage from '@/assets/tooling-&-explorers/iexec-explorer/explorer-global.png';
 import dealViewImage from '@/assets/tooling-&-explorers/iexec-explorer/deal-view.png';
 import taskViewImage from '@/assets/tooling-&-explorers/iexec-explorer/task-view.png';
-import taskDetailsStartedImage from '@/assets/tooling-&-explorers/iexec-explorer/task-details-started.png';
 import taskDetailsCompletedImage from '@/assets/tooling-&-explorers/iexec-explorer/task-details-completed.png';
 import appViewImage from '@/assets/tooling-&-explorers/iexec-explorer/app-view.png';
 import datasetViewImage from '@/assets/tooling-&-explorers/iexec-explorer/dataset-view.png';
 import workerpoolViewImage from '@/assets/tooling-&-explorers/iexec-explorer/workerpool-view.png';
+import assetTypesAdvanceFilterViewImage from '@/assets/tooling-&-explorers/iexec-explorer/asset-types-advance-filter.png';
 </script>
diff --git a/src/guides/build-iapp/inputs.md b/src/guides/build-iapp/inputs.md
index dff3d127..10810d71 100644
--- a/src/guides/build-iapp/inputs.md
+++ b/src/guides/build-iapp/inputs.md
@@ -413,7 +413,8 @@ Add your App Secret to the project configuration:
 
 ### How to Access App Secrets
 
-App secrets are exposed as environment variables following the `IEXEC_APP_DEVELOPER_SECRET` naming pattern.
+App secrets are exposed as environment variables following the
+`IEXEC_APP_DEVELOPER_SECRET` naming pattern.
 
 ::: code-group
 
diff --git a/src/guides/manage-data/handle-schemas-dataset-types.md b/src/guides/manage-data/handle-schemas-dataset-types.md
index 5daeb9eb..590d2f4c 100644
--- a/src/guides/manage-data/handle-schemas-dataset-types.md
+++ b/src/guides/manage-data/handle-schemas-dataset-types.md
@@ -16,6 +16,11 @@ Think of schemas as **data fingerprints** - they tell iApp "this protected data
 contains an email address and a phone number" without revealing the actual
 values.
 
+Use the
+<a :href="`${explorerUrl}/datasets`" target="_blank" rel="noopener">iExec
+explorer</a> to browse protected data and see their asset types. Make filtered
+searches based on schema to find data that fits your needs.
+
 ## How schemas work
 
 When you protect data with DataProtector, the SDK automatically analyzes your
@@ -131,6 +136,10 @@ const listProtectedData = await dataProtectorCore.getProtectedData({
 
 ## Real examples
 
+For real-world applications built by developers using various asset types, check
+out the [iExec case studies](https://www.iex.ec/case-studies) to see how schemas
+are used in production environments.
+
 ### Simple User Profile
 
 ```ts twoslash
@@ -269,3 +278,17 @@ explore next:
   for running computations
 - **See it in action**: Try our [Hello World tutorial](/get-started/helloWorld)
   for a complete example
+
+<script setup>
+import { computed } from 'vue';
+import useUserStore  from '@/stores/useUser.store';
+import {getChainById} from '@/utils/chain.utils';
+import ImageViewer from '@/components/ImageViewer.vue';
+
+// Get current chain info
+const userStore = useUserStore();
+const selectedChain = computed(() => userStore.getCurrentChainId());
+
+const chainData = computed(() => getChainById(selectedChain.value));
+const explorerUrl = computed(() => chainData.value.iexecExplorerUrl);
+</script>
diff --git a/src/references/dataProtector/dataProtectorCore/processProtectedData.md b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
index 646624c6..234cb51f 100644
--- a/src/references/dataProtector/dataProtectorCore/processProtectedData.md
+++ b/src/references/dataProtector/dataProtectorCore/processProtectedData.md
@@ -208,8 +208,7 @@ const processProtectedDataResponse =
 
 Do not use this to provide any sensitive information to the application. All
 arguments passed this way are visible in plain text using the
-<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
-explorer</a> .
+<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
 
 :::
 
@@ -448,8 +447,7 @@ import { type ProcessProtectedDataResponse } from '@iexec/dataprotector';
 
 The ID of the transaction that happened on iExec's side chain. You may view
 details on the transaction using the
-<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
-explorer</a> .
+<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
 
 ### dealId
 
@@ -463,8 +461,7 @@ Identifies the specific deal associated with this transaction.
 
 A unique identifier associated with a task currently running on the iExec
 protocol. You can monitor task execution using the
-<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
-explorer</a> .
+<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
 
 ::: tip
 
diff --git a/src/references/web3mail/methods/sendEmail.md b/src/references/web3mail/methods/sendEmail.md
index 76543d45..5422b1de 100644
--- a/src/references/web3mail/methods/sendEmail.md
+++ b/src/references/web3mail/methods/sendEmail.md
@@ -313,8 +313,7 @@ import { type SendEmailResponse } from '@iexec/web3mail';
 
 This uniquely identifies the email task on the iExec side chain. You can view
 the status of the `sendEmail` method by monitoring the task on the
-<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
-explorer</a> .
+<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
 
 ## Error Handling
 
diff --git a/src/references/web3telegram/methods/sendTelegram.md b/src/references/web3telegram/methods/sendTelegram.md
index bd0a835c..ed607288 100644
--- a/src/references/web3telegram/methods/sendTelegram.md
+++ b/src/references/web3telegram/methods/sendTelegram.md
@@ -281,8 +281,7 @@ import { type SendTelegramResponse } from '@iexec/web3telegram';
 
 This uniquely identifies the telegram task on the iExec side chain. You can view
 the status of the `sendTelegram` method by monitoring the task on the
-<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
-explorer</a> .
+<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .
 
 <script setup>
 import { computed } from 'vue';