← previous blocknext block →recent activity

Analyzing

Block #102,218,634

21 transactions · 21 stateful · 2026-09-05 15:20:03 UTC

Parallelism

86/100

Blocked

24%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,218,634  ·  21 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

0x045532dd…4b7d

0x34b655…2a6f

4 touches
1 conflict

0x1dc71894…1884

0x34b655…2a6f

4 touches
1 conflict

0x24b6eb34…84cd

0x34b655…2a6f

4 touches
1 conflict

0x26c599c1…706c

0x34b655…2a6f

4 touches
1 conflict

0x2f17174f…68b4

0x34b655…2a6f

4 touches
1 conflict

0x3774a68c…11ff

0x34b655…2a6f

4 touches
1 conflict

0x479dd2a9…a74f

0x34b655…2a6f

4 touches
1 conflict

0x4b024b98…8f37

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

1 conflict on slot 0x045532dd4b…244b7d

← previous block·next block →recent activity