← previous blocknext block →recent activity

Analyzing

Block #93,923,781

7 transactions · 7 stateful · 2026-08-07 12:48:29 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,923,781  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x1630d4a2…34a7

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x19b4e3fd…3821

0x34b655…2a6f

2 touches
0 conflicts

0x2965e2d6…5800

0x34b655…2a6f

2 touches
0 conflicts

0x454cdf57…aebc

0x34b655…2a6f

2 touches
0 conflicts

0x45885570…ed97

0x34b655…2a6f

2 touches
0 conflicts

0x7cbbf8d5…4b14

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x1630d4a21f…6834a7

← previous block·next block →recent activity