← previous blocknext block →recent activity
Analyzing
Block #107,441,110
12 transactions · 12 stateful · 2026-09-23 22:31:46 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,441,110 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w18w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ad7e7c3…293b
0x34b655…2a6f
6 touches
3 conflicts
0x41f0f7a7…f84c
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x56f91464…1e91
0x37db7f…ec7b
4 touches
1 conflict
0x640481cc…a2df
0x37db7f…ec7b
4 touches
1 conflict
0x8a35acfb…d1b0
0x37db7f…ec7b
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 0x7ad7e7c31d…8c293b
Audit this contract →
← previous block·next block →recent activity