← previous blocknext block →recent activity

Analyzing

Block #93,364,407

21 transactions · 20 stateful · 2026-08-05 13:55:53 UTC

Parallelism

76/100

Blocked

40%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,364,407  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xfd42a6b9…4c81

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xe3716626…7d68

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4acbdbcf…a8c6

0x34b655…2a6f

4 touches
1 conflict

0x4c214bb3…c5d3

0x34b655…2a6f

4 touches
1 conflict

0x562a4a30…f8d5

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity