← previous blocknext block →recent activity
Analyzing
Block #106,934,109
28 transactions · 27 stateful · 2026-09-22 03:59:25 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,934,109 · 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
1w07w08w110w011w112w213w314w415w216w318w122w423w524w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa60abeec…16c2
0x34b655…2a6f
12 touches
15 conflicts
0x73a0005f…70a8
0x34b655…2a6f
10 touches
10 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x51087f5a…61f7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
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
15 conflicts on slot 0xa60abeecf9…2116c2
Audit this contract →
← previous block·next block →recent activity