← previous blocknext block →recent activity
Analyzing
Block #106,187,249
22 transactions · 19 stateful · 2026-09-19 13:19:25 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.86
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,187,249 · 22 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
1w03w14w17w28w311w413w514w615w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xaad8379a…34a0
0x34b655…2a6f
10 touches
10 conflicts
0xc4184a2d…31f9
0x34b655…2a6f
8 touches
6 conflicts
0x9430e759…86df
0x34b655…2a6f
6 touches
3 conflicts
0x61037d3e…1885
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity