← previous blocknext block →recent activity
Analyzing
Block #111,072,425
23 transactions · 19 stateful · 2026-10-06 15:21:50 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #111,072,425 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w09w110w211w216w317w421w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1028dc64…a3c8
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0f94ee4c…1897
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x4dd46dc6…39b8
0xd32edf…ff58
5 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
6 conflicts on slot 0x1028dc64ad…81a3c8
Audit this contract →
← previous block·next block →recent activity