← previous blocknext block →recent activity
Analyzing
Block #110,321,909
14 transactions · 14 stateful · 2026-10-04 00:21:12 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,321,909 · 14 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
6w07w18w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c211514…b757
0x34b655…2a6f
8 touches
6 conflicts
0xb4656137…5858
0x34b655…2a6f
8 touches
6 conflicts
0x5bf29e70…4100
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x99601df7…7339
0x34b655…2a6f
4 touches
1 conflict
0x68736137…69dc
0x34b655…2a6f
4 touches
1 conflict
0x3428b104…852a
0x34b655…2a6f
3 touches
1 conflict
0xe274ec82…e88b
0x34b655…2a6f
3 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 0x8c21151476…60b757
Audit this contract →
← previous block·next block →recent activity