← previous blocknext block →recent activity
Analyzing
Block #108,533,251
24 transactions · 21 stateful · 2026-09-27 18:10:40 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,533,251 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w011w112w213w314w418w119w220w021w122w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b780b26…f5ff
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0x5969523e…5191
0x34b655…2a6f
8 touches
6 conflicts
0x88fc2a68…3918
0x34b655…2a6f
8 touches
6 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
8 touches
6 conflicts
0xa68df040…9b48
0x34b655…2a6f
8 touches
6 conflicts
0xada087b9…4aca
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 0x8b780b2668…85f5ff
Audit this contract →
← previous block·next block →recent activity