← previous blocknext block →recent activity
Analyzing
Block #106,950,031
28 transactions · 22 stateful · 2026-09-22 05:19:33 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,950,031 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w112w213w316w320w221w422w523w424w526w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x582c9575…ed8c
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc953c572…34b1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0x090878b5…683f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
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
10 conflicts on slot 0x582c957584…18ed8c
Audit this contract →
← previous block·next block →recent activity