← previous blocknext block →recent activity
Analyzing
Block #106,235,525
24 transactions · 23 stateful · 2026-09-19 17:22:28 UTC
Parallelism
63/100
Blocked
48%
Avg conflicts / tx
1.58
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,235,525 · 24 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
1w03w15w06w18w29w315w416w517w618w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
16 touches
28 conflicts
0x7fd1b446…9abe
0x34b655…2a6f
12 touches
15 conflicts
0x7049c44f…3939
0x34b655…2a6f
10 touches
10 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
8 touches
6 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity