← previous blocknext block →recent activity
Analyzing
Block #108,444,261
17 transactions · 13 stateful · 2026-09-27 10:42:42 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,444,261 · 17 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
2w03w04w16w18w09w111w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffdacbf9…a046
0x34b655…2a6f
6 touches
3 conflicts
0x09beabbc…065e
0x188d58…ea8e
4 touches
1 conflict
0x24c5620c…7ac5
0x34b655…2a6f
4 touches
1 conflict
0x34886fd6…6f1f
0x34b655…2a6f
4 touches
1 conflict
0x51a145e3…9c9c
0x34b655…2a6f
4 touches
1 conflict
0x5c62fe6a…f144
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
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 0xffdacbf94f…50a046
Audit this contract →
← previous block·next block →recent activity