← previous blocknext block →recent activity
Analyzing
Block #110,380,868
24 transactions · 21 stateful · 2026-10-04 05:17:49 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,380,868 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w310w011w113w222w023w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x6e831143…b588
0x34b655…2a6f
4 touches
1 conflict
0x739123da…57f3
0x34b655…2a6f
4 touches
1 conflict
0x8f4256a9…d890
0x34b655…2a6f
4 touches
1 conflict
0x9abad0e8…28a3
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 0xfdd40e24dd…99dca0
Audit this contract →
← previous block·next block →recent activity