← previous blocknext block →recent activity

Analyzing

Block #106,546,127

23 transactions · 22 stateful · 2026-09-20 19:25:39 UTC

Parallelism

70/100

Blocked

32%

Avg conflicts / tx

0.74

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,546,127  ·  23 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

0xd228e29a…a108

0x34b655…2a6f

10 touches
10 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

6 touches
3 conflicts

0xf788c790…e66f

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xfe2577ac…677b

0x34b655…2a6f

4 touches
1 conflict

0x7fec4dea…6005

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd19f77b9…84f7

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

10 conflicts on slot 0xd228e29a5c…2ba108

← previous block·next block →recent activity