← previous blocknext block →recent activity
Analyzing
Block #110,392,845
20 transactions · 17 stateful · 2026-10-04 06:18:05 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #110,392,845 · 20 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
1w02w13w24w38w012w013w414w517w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x6432b7bf…660c
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0x0a3faaed…8179
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xccaf39a6…2e41
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x7954ece9af…e7fef0
Audit this contract →
← previous block·next block →recent activity