← previous blocknext block →recent activity
Analyzing
Block #109,143,097
9 transactions · 9 stateful · 2026-09-29 21:27:14 UTC
Parallelism
44/100
Blocked
56%
Avg conflicts / tx
1.22
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,143,097 · 9 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
1w02w13w24w36w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x500e6948…adc3
0x34b655…2a6f
8 touches
6 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
8 touches
6 conflicts
0x19eb6f0d…3cac
0xd32edf…ff58
7 touches
6 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x7499cc33…a306
0x34b655…2a6f
6 touches
3 conflicts
0x764dd399…b9fd
0x34b655…2a6f
6 touches
3 conflicts
0x98dd86bb…1edb
0x34b655…2a6f
6 touches
3 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 0x500e69487d…3badc3
Audit this contract →
← previous block·next block →recent activity