← previous blocknext block →recent activity
Analyzing
Block #110,220,554
25 transactions · 24 stateful · 2026-10-03 15:51:14 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #110,220,554 · 25 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
4w05w16w27w38w49w510w613w014w123w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
8 touches
6 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x241b55d6…e0fa
0x34b655…2a6f
8 touches
6 conflicts
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0xf29cfd47…fca3
0x34b655…2a6f
8 touches
6 conflicts
0xb4656137…5858
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 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
21 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity