← previous blocknext block →recent activity
Analyzing
Block #110,380,174
25 transactions · 23 stateful · 2026-10-04 05:14:20 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.76
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #110,380,174 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w36w47w513w618w322w623w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0x38524fae…9deb
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
8 touches
6 conflicts
0x3347cbe5…846c
0x34b655…2a6f
8 touches
6 conflicts
0x3643741b…109c
0x34b655…2a6f
8 touches
6 conflicts
0x8d5914d7…8eba
0x34b655…2a6f
8 touches
6 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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity