← previous blocknext block →recent activity
Analyzing
Block #109,133,817
25 transactions · 23 stateful · 2026-09-29 20:40:32 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,133,817 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w110w211w314w015w116w217w318w322w023w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67318be2…6e11
0x34b655…2a6f
10 touches
10 conflicts
0x742e5c25…a6b2
0x34b655…2a6f
10 touches
10 conflicts
0x36f921ef…b75f
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
8 touches
6 conflicts
0x7499cc33…a306
0x34b655…2a6f
8 touches
6 conflicts
0x85e2939a…902a
0x34b655…2a6f
8 touches
6 conflicts
0x932f2399…b7fe
0x34b655…2a6f
8 touches
6 conflicts
0x98dd86bb…1edb
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
10 conflicts on slot 0x67318be28b…f86e11
Audit this contract →
← previous block·next block →recent activity