← previous blocknext block →recent activity
Analyzing
Block #106,471,561
25 transactions · 23 stateful · 2026-09-20 13:10:23 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
2.28
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,471,561 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w28w29w314w415w516w617w718w619w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2d62758…d600
0x34b655…2a6f
16 touches
28 conflicts
0x1c840894…764a
0x34b655…2a6f
14 touches
21 conflicts
0x4118bd12…924a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
8 touches
6 conflicts
0x2d5b40dc…27c9
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x739cf558…6266
0x34b655…2a6f
8 touches
6 conflicts
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
28 conflicts on slot 0xf2d627585b…40d600
Audit this contract →
← previous block·next block →recent activity