← previous blocknext block →recent activity
Analyzing
Block #110,220,683
24 transactions · 21 stateful · 2026-10-03 15:51:53 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #110,220,683 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w512w613w716w620w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
16 touches
28 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0x8c211514…b757
0x34b655…2a6f
8 touches
6 conflicts
0xb4656137…5858
0x34b655…2a6f
8 touches
6 conflicts
0x10f0a1bf…12c3
0x34b655…2a6f
6 touches
3 conflicts
0x5bf29e70…4100
0x34b655…2a6f
6 touches
3 conflicts
0xe01c766d…74bd
0x34b655…2a6f
5 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
28 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity