Dezenmart Admin

The console the Dezenmart team runs the marketplace from.

When: 2025
Kind: Marketplace operations console
Role: Frontend engineer
Stack: React 19, TypeScript, Tailwind CSS 4, Recharts, Vite

Dezenmart admin dashboard with sales, escrow balance, orders, vendors and a revenue chart

The console Dezenmart's team runs the marketplace from: a dashboard of marketplace activity, the payments ledger, dispute handling and control over vendors. Staff sign in with Google.

What it covers

A dashboard charts marketplace activity with Recharts: sales, the escrow balance, orders, active vendors, and revenue against expenses. Payments shows platform profit, what is still held in escrow, gas costs, and the contract address every payment routes through. Disputes collects the orders a buyer has contested, and vendor control decides who sells.

The screens here run on the console's built-in placeholder data, so no real order, vendor or customer appears.

Order paidFunds held in escrow
Dispute raisedBy the buyer
ReviewedIn the admin console
ResolvedReleased or refunded

Where a disputed order goes

Disputes table with order numbers, users, dates, statuses, vendors and reasons — Fig. 1Disputes: every contested order, its status and the vendor involved.

Vendor control table with store names, join dates, statuses and product counts — Fig. 2Vendor control: active, pending or blocked.

Payments page with profit, pending escrow, gas fee, the payment contract address and payment history — Fig. 3Payments, and the contract address payments route through.

DezentraNext project: Cross-chain commerce