← previous blocknext block →recent activity
Analyzing
Block #110,380,898
14 transactions · 14 stateful · 2026-10-04 05:17:58 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,380,898 · 14 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
4w05w110w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0x2902912b…448c
0x34b655…2a6f
4 touches
1 conflict
0x3abf7ba7…5d01
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x5961f9aa…5fe2
0x34b655…2a6f
4 touches
1 conflict
0x8f4256a9…d890
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
6 conflicts on slot 0xfdd40e24dd…99dca0
Audit this contract →
← previous block·next block →recent activity