← previous blocknext block →recent activity
Analyzing
Block #106,466,109
20 transactions · 18 stateful · 2026-09-20 12:42:56 UTC
Parallelism
45/100
Blocked
61%
Avg conflicts / tx
2.7
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,466,109 · 20 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w310w411w512w613w714w815w916w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2d6864a…723c
0x34b655…2a6f
18 touches
36 conflicts
0x7bb6424f…59b8
0x34b655…2a6f
16 touches
28 conflicts
0xb1927b58…f161
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
10 touches
10 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0x810a3aa2…0227
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 0xf2d6864ab6…ac723c
Audit this contract →
← previous block·next block →recent activity