> For the complete documentation index, see [llms.txt](https://docs.blockrazor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockrazor.io/transaction-submission/block-builder/bundle-explorer.md).

# BSC Block Builder Bundle Explorer

{% hint style="info" %}
Bundle Explorer is packaged with the Bundle Tracing service. Users who purchase Bundle Tracing can access Bundle Explorer after signing in to the BlockRazor Portal.
{% endhint %}

## BSC Bundle Explorer

### Product Definition

BSC Bundle Explorer is a block and bundle data exploration tool built by BlockRazor for the BSC Block Builder ecosystem.

It presents block rewards and bundle rewards from three perspectives: blocks, dates, and validators. Users can also inspect the bundles and transaction composition within a block. This helps searchers, builders, validators, and researchers understand on-chain bundle execution and reward performance.

### Core Capabilities

#### Block Reward

View BSC blocks, validators, block rewards, bundle counts, and bundle rewards. Users can search by block number and expand an individual block to inspect its bundles and transaction details, including addresses, gas used, gas price, and transaction fees.

<div><figure><img src="/files/EO3NGzV9BGz6pCd85kuq" alt=""><figcaption></figcaption></figure> <figure><img src="/files/jYufsPHp3x6jHlqX6gdC" alt=""><figcaption></figcaption></figure></div>

#### Daily Reward

Review daily totals for blocks, bundles, block rewards, bundle rewards, and the highest bundle reward. This provides a clear view of BSC bundle activity and reward trends over time.

<figure><img src="/files/X3LW4gT6IoDInQ1rLFif" alt="" width="375"><figcaption></figcaption></figure>

#### Validator Reward

View block rewards and bundle rewards for different validators on a selected date. This makes it easier to compare validator reward performance and composition.

<figure><img src="/files/Cow8I8ma36vQ5PUNNu04" alt="" width="375"><figcaption></figcaption></figure>

### Use Cases

* **Searcher strategy review**: Confirm whether a bundle was included in a block and inspect its transaction composition, including 0 Gwei transactions.
* **Builder and validator analysis**: Compare block rewards and bundle rewards to understand validator performance.
* **On-chain research**: Track daily bundle volume and reward changes to observe activity across the BSC bundle market.
* **Issue investigation**: Start from a block number and drill down into bundles and transactions to verify on-chain execution results.

### Product Value

BSC Bundle Explorer brings block, bundle, transaction, and validator data into one interface, reducing the cost of manual on-chain research and data collection. Users can review strategies, analyze rewards, and investigate execution issues more efficiently while gaining a unified view of bundle activity across the BSC Block Builder ecosystem.

### Data Notes

* All reward values are displayed in BNB.
* Block Reward displays blocks produced at least five minutes ago.
* Daily Reward data is updated every 24 hours.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.blockrazor.io/transaction-submission/block-builder/bundle-explorer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
