← previous blocknext block →recent activity
Analyzing
Block #106,565,811
21 transactions · 20 stateful · 2026-09-20 21:04:43 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
2.14
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,565,811 · 21 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
1w02w03w16w19w211w312w413w514w615w716w820w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb81366e…406c
0x34b655…2a6f
18 touches
36 conflicts
0x4089d428…b018
0x34b655…2a6f
12 touches
15 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
10 touches
10 conflicts
0x2c2761c0…476e
0x34b655…2a6f
10 touches
10 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
10 touches
10 conflicts
0xa2087bfa…b8a9
0x34b655…2a6f
10 touches
10 conflicts
0x3ca00e15…9c15
0x34b655…2a6f
8 touches
6 conflicts
0xf8f9ab7b…78bd
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xdb81366ee2…be406c
Audit this contract →
← previous block·next block →recent activity