← previous blocknext block →recent activity
Analyzing
Block #110,135,274
13 transactions · 9 stateful · 2026-10-03 08:42:07 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #110,135,274 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0x27daa6a5…11a4
0x34b655…2a6f
4 touches
1 conflict
0xbfd2a6e6…f7ef
0x34b655…2a6f
4 touches
1 conflict
0xfdd40e24…dca0
0x34b655…2a6f
4 touches
1 conflict
0xbc586a3e…f43c
0x34b655…2a6f
2 touches
0 conflicts
0xc5a57f2a…b15b
0x34b655…2a6f
2 touches
0 conflicts
0xccebf5c5…8758
0x34b655…2a6f
2 touches
0 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7954ece9af…e7fef0
Audit this contract →
← previous block·next block →recent activity