← previous blocknext block →recent activity

Analyzing

Block #106,185,232

19 transactions · 18 stateful · 2026-09-19 13:09:16 UTC

Parallelism

63/100

Blocked

44%

Avg conflicts / tx

0.89

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,185,232  ·  19 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

0xc2a5cb78…d4c1

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x51f1f20c…d9da

0x34b655…2a6f

6 touches
3 conflicts

0xab981df1…2941

0x34b655…2a6f

6 touches
3 conflicts

0x315e07b8…9823

0x34b655…2a6f

4 touches
1 conflict

0x40a9339c…6572

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4abfb389…18f4

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 0xc2a5cb783d…3bd4c1

← previous block·next block →recent activity