Optional indexed-log and contract-creation fallback. The key is not hardcoded or saved; browser requests can expose it to the browser user.
Used as the starting block for All time analytics and full partner history. Find it on the contract creation transaction in BscScan.
ABI is embedded. Read-only RPC access is sufficient; wallet connection is not required.
Enter an RPC URL, then connect. You can use a public BNB Chain RPC or a provider URL.
ANALYTICS WINDOW
Default view is the latest 30 days. All-time history starts at the Deployment block entered above. If left blank, the dashboard attempts automatic discovery using BscScan or historical RPC access.
Lifetime buy volume
—
USDT · contract aggregate
Lifetime sell volume
—
INRP · contract aggregate
Lifetime trades
—
Buy + sell aggregate
Adapter fee rate
—
Basis points
Period buy trades
—
AnalyticsTradeRecorded events
Period sell trades
—
AnalyticsTradeRecorded events
Period partner allocations
—
PartnerFeeAllocated events
Period fee claims
—
PartnerFeesClaimed events
Trade activity
Last 30 daysScan historical events to populate chart
Daily trade count from AnalyticsTradeRecorded. Buy and sell are separate series.
Contract status
Owner—
Paused—
Automatic fee transfer—
Trading volume trend
Scan events to populate chart
Buy volume is denominated in USDT; sell volume is denominated in INRP. They are not added together.
Fee allocation trend
Scan fee allocation events
Partner and owner allocations shown as event counts in this overview chart. Token amounts are shown in fee detail panels.
Buy volume · USDT
Scan events to populate chart
Sell volume · INRP
Scan events to populate chart
Buy vs sell trades
Scan events to populate chart
Trade execution details
Buy forwards—
Sell forwards—
Trade authorizations—
Unique traders in scan—
Partner performance · top partners by buy volume
Scan partner/trade events
Registered partners
Unique registered partners found
—
Directory is reconstructed from PartnerRegistered history and enriched with live contract getters. Default is all time.
| Partner wallet | Referral code | Payout address | Status | Share | Auto payout | Accrued USDT | Accrued INRP | Registered |
|---|---|---|---|---|---|---|---|---|
| Connect, enter the Deployment block above (or allow automatic discovery), then load the full partner directory. | ||||||||
Partner lookup
Buy volume
—
USDT
Sell volume
—
INRP
Commission earned
—
USDT / INRP
Commission claimed
—
USDT / INRP
| Enter a partner address to read registration, payout mode, share, accrued fees and stats. |
User analytics lookup
Buy volume
—
USDT
Sell volume
—
INRP
Buy / sell trades
—
Count
Fees paid
—
USDT / INRP
| User stats, nonce and recent scanned event activity will appear here. |
Users observed in selected event range
| User | Buy trades | Sell trades | Buy volume (USDT) | Sell volume (INRP) | Partners attributed |
|---|---|---|---|---|---|
| Scan AnalyticsTradeRecorded events to build this table | |||||
USDT fee accounting
| Connect to load accounting |
INRP fee accounting
| Connect to load accounting |
Fee balances & treasury
| Connect to load balances |
Partner liabilities
| Connect to load liabilities |
Fee flow events
Scan fee events to populate chart
Event amounts retain token denomination; USDT and INRP are never summed into a common total.
Ownership & operating controls
| Connect to load state |
Fee configuration
| Connect to load configuration |
Partner security / configuration events
| Block | Event | Partner / account | Details | Transaction |
|---|---|---|---|---|
| Scan admin events to populate history | ||||
Historical event explorer
0 events loaded
| Block | Event | Wallet / token | Summary | Transaction |
|---|---|---|---|---|
| No events loaded | ||||
Historical index & local cache
Event scan results are cached locally in this browser. Cache is specific to the adapter address and selected scan data.
Historical charts are based on events returned by your RPC provider for the scanned block range. Some public RPCs cap block ranges, log response size or historical access. If a scan fails, reduce chunk size or use an archive-capable RPC. A partial scan is labelled as partial and must not be interpreted as full-period history.
Scan diagnostics
Raw logs returned
0
Recognized / decoded
0
Parse errors
0
Data source
—
No scan has run.
No logs and ABI mismatch are reported separately after scanning.