← previous blocknext block →recent activity

Analyzing

Block #93,280,197

10 transactions · 10 stateful · 2026-08-05 06:52:30 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,280,197  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9ff176a9…152e

0x065c9d…c394

4 touches
1 conflict

0x0e8df236…f155

0x34b655…2a6f

4 touches
1 conflict

0x63a8652c…5b43

0x34b655…2a6f

4 touches
1 conflict

0x63a8652c…5b44

0x34b655…2a6f

4 touches
1 conflict

0x6474161a…6a37

0x34b655…2a6f

4 touches
1 conflict

0x6a4b11f5…0087

0x34b655…2a6f

4 touches
1 conflict

0xeedd4295…4ec4

0x34b655…2a6f

3 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: Market-MON/USDC

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity