← previous blocknext block →recent activity
Analyzing
Block #108,969,676
26 transactions · 18 stateful · 2026-09-29 06:52:18 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,969,676 · 26 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
15w016w117w218w319w220w421w524w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x0d09ca5e…a511
0x34b655…2a6f
6 touches
3 conflicts
0x6c138c5f…ea45
0x34b655…2a6f
6 touches
3 conflicts
0x91614897…7c7d
0x34b655…2a6f
6 touches
3 conflicts
0xc53799eb…d928
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x46483cb1…e7ca
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 0xf6deafb553…9e5c25
Audit this contract →
← previous block·next block →recent activity