← previous blocknext block →recent activity
Analyzing
Block #109,137,627
19 transactions · 14 stateful · 2026-09-29 20:59:42 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,137,627 · 19 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
3w04w16w27w08w311w116w018w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe569004f…0228
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x487cc6ea…24a5
0x34b655…2a6f
6 touches
3 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
4 touches
1 conflict
0x742e5c25…a6b2
0x34b655…2a6f
4 touches
1 conflict
0x7499cc33…a306
0x34b655…2a6f
4 touches
1 conflict
0x85e2939a…902a
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
3 conflicts on slot 0xe569004f07…1d0228
Audit this contract →
← previous block·next block →recent activity