← previous blocknext block →recent activity
Analyzing
Block #107,650,850
22 transactions · 22 stateful · 2026-09-24 16:08:11 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,650,850 · 22 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
3w04w16w07w011w112w213w214w315w016w117w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ee13d39…476d
0x34b655…2a6f
6 touches
3 conflicts
0x51e96b98…de36
0x34b655…2a6f
6 touches
3 conflicts
0x1393df1d…afbd
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xed8224d3…528e
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 0x5ee13d39d9…3e476d
Audit this contract →
← previous block·next block →recent activity