← previous blocknext block →recent activity
Analyzing
Block #108,503,515
20 transactions · 16 stateful · 2026-09-27 15:41:00 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,503,515 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w29w010w112w314w317w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fa6e1a0…c881
0x34b655…2a6f
8 touches
6 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x7006165a…df17
0x34b655…2a6f
6 touches
3 conflicts
0x8eac5088…e823
0x34b655…2a6f
6 touches
3 conflicts
0x90f65937…f295
0x34b655…2a6f
6 touches
3 conflicts
0x9d8078fe…ed70
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x5fa6e1a013…9dc881
Audit this contract →
← previous block·next block →recent activity