← previous blocknext block →recent activity
Analyzing
Block #110,380,415
18 transactions · 18 stateful · 2026-10-04 05:15:33 UTC
Parallelism
61/100
Blocked
33%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #110,380,415 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w112w013w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xbdb641bb…3a65
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x15d039e7…4bb6
0x34b655…2a6f
4 touches
1 conflict
0xd739490d…821e
0x34b655…2a6f
4 touches
1 conflict
0xfdd40e24…dca0
0x34b655…2a6f
4 touches
1 conflict
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity