← previous blocknext block →recent activity

Analyzing

Block #106,934,501

21 transactions · 21 stateful · 2026-09-22 04:01:23 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,934,501  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x51087f5a…61f7

0x34b655…2a6f

14 touches
21 conflicts

0xccebf5c5…8758

0x34b655…2a6f

12 touches
15 conflicts

0xee192525…bd26

0x34b655…2a6f

12 touches
15 conflicts

0x7dd96c96…7335

0x34b655…2a6f

4 touches
1 conflict

0x9375a764…dca1

0x34b655…2a6f

4 touches
1 conflict

0xa4658f5c…b257

0x34b655…2a6f

4 touches
1 conflict

0xa9988419…9f45

0x34b655…2a6f

4 touches
1 conflict

0xab981df1…2941

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

21 conflicts on slot 0x51087f5abf…f061f7

← previous block·next block →recent activity