← previous blocknext block →recent activity
Analyzing
Block #107,450,685
9 transactions · 9 stateful · 2026-09-23 23:19:57 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,450,685 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4d08970…f9b8
0x34b655…2a6f
4 touches
1 conflict
0xdced4209…6afa
0x34b655…2a6f
4 touches
1 conflict
0xf51a94f0…f9b9
0x34b655…2a6f
4 touches
1 conflict
0x3b8da5cc…e045
0x34b655…2a6f
4 touches
1 conflict
0xb0229edc…60f2
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x5f83c9e9…68e0
0x34b655…2a6f
2 touches
0 conflicts
0x9122db17…e8f2
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc4d0897047…5cf9b8
Audit this contract →
← previous block·next block →recent activity