← previous blocknext block →recent activity
Analyzing
Block #109,131,769
30 transactions · 25 stateful · 2026-09-29 20:30:14 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,131,769 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w111w212w313w014w315w416w517w618w719w221w829w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5305ab8a…2ec9
0x34b655…2a6f
12 touches
15 conflicts
0xc5ac4b35…7e68
0x34b655…2a6f
10 touches
10 conflicts
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x06d6349e…686d
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
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 0x5305ab8ad9…d92ec9
Audit this contract →
← previous block·next block →recent activity