← previous blocknext block →recent activity
Analyzing
Block #108,433,796
18 transactions · 14 stateful · 2026-09-27 09:50:01 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,433,796 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w210w312w013w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x199a4f01…2183
0x34b655…2a6f
8 touches
6 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
8 touches
6 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
8 touches
6 conflicts
0x3643d7c6…4925
0x34b655…2a6f
8 touches
6 conflicts
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
8 touches
6 conflicts
0x6f3b84d3…2d61
0x34b655…2a6f
8 touches
6 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x199a4f01e1…f72183
Audit this contract →
← previous block·next block →recent activity