← previous blocknext block →recent activity

Analyzing

Block #93,512,547

24 transactions · 23 stateful · 2026-08-06 02:20:39 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,512,547  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x53e32fce…a5d8

0x34b655…2a6f

6 touches
3 conflicts

0x2c390858…b1ed

0x34b655…2a6f

6 touches
3 conflicts

0x2840c278…bbc7

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x3d2c514e…49b1

0x34b655…2a6f

4 touches
1 conflict

0x63bed776…8d4a

0x34b655…2a6f

4 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: Perpl

3 conflicts on slot 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity