← previous blocknext block →recent activity
Analyzing
Block #110,392,213
19 transactions · 17 stateful · 2026-10-04 06:14:55 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,392,213 · 19 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
1w02w13w04w15w26w312w013w1
- 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
0xfac61869…a55d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cc61cd1…d304
0x34b655…2a6f
4 touches
1 conflict
0x5483bd07…cfb1
0x34b655…2a6f
4 touches
1 conflict
0x6224915c…e9bf
0x34b655…2a6f
4 touches
1 conflict
0x2a4f488f…d8ec
0xf42df8…ad97
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