← previous blocknext block →recent activity

Analyzing

Block #93,843,779

17 transactions · 16 stateful · 2026-08-07 06:05:50 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,843,779  ·  17 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

0xfed09e59…a493

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x1bb56de3…732e

0x34b655…2a6f

4 touches
1 conflict

0x2fd12b6c…02cc

0x34b655…2a6f

4 touches
1 conflict

0x3d158563…8713

0x34b655…2a6f

4 touches
1 conflict

0x5fde4971…aac9

0x34b655…2a6f

4 touches
1 conflict

0x92fa1dc0…b23a

0x34b655…2a6f

4 touches
1 conflict

0xaa11c68c…ac7f

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 0xfed09e59c7…d6a493

← previous block·next block →recent activity