← previous blocknext block →recent activity
Analyzing
Block #109,143,011
17 transactions · 14 stateful · 2026-09-29 21:26:48 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,143,011 · 17 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
1w04w15w26w39w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1032f16c…a9b1
0x34b655…2a6f
8 touches
6 conflicts
0x241b55d6…e0fa
0x34b655…2a6f
8 touches
6 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
8 touches
6 conflicts
0x500e6948…adc3
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
8 touches
6 conflicts
0x7499cc33…a306
0x34b655…2a6f
8 touches
6 conflicts
0x764dd399…b9fd
0x34b655…2a6f
8 touches
6 conflicts
0x7d9ef283…ddd1
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 0x1032f16c0e…4fa9b1
Audit this contract →
← previous block·next block →recent activity