← previous blocknext block →recent activity
Analyzing
Block #107,666,713
24 transactions · 19 stateful · 2026-09-24 17:28:32 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,666,713 · 24 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
4w05w18w09w110w116w017w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x3a663e9a…a9d1
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9ca
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9cb
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9cd
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9ce
0x508254…98bd
4 touches
1 conflict
0x1393df1d…afbd
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity