← previous blocknext block →recent activity
Analyzing
Block #109,143,320
21 transactions · 18 stateful · 2026-09-29 21:28:21 UTC
Parallelism
57/100
Blocked
44%
Avg conflicts / tx
1.76
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,143,320 · 21 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
3w04w15w26w37w48w59w610w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
18 touches
36 conflicts
0x500e6948…adc3
0x34b655…2a6f
18 touches
36 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
16 touches
28 conflicts
0x5969523e…5191
0x34b655…2a6f
16 touches
28 conflicts
0x7499cc33…a306
0x34b655…2a6f
16 touches
28 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
16 touches
28 conflicts
0x21bce2a9…2469
0x34b655…2a6f
16 touches
28 conflicts
0xdad13823…6798
0x37db7f…ec7b
16 touches
28 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
36 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity