← previous blocknext block →recent activity
Analyzing
Block #112,583,911
23 transactions · 21 stateful · 2026-10-11 22:08:27 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,583,911 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w011w112w213w214w315w316w417w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdacb24f7…56ce
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0x3e1329b8…deca
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xcb8ee643…a05a
0x34b655…2a6f
6 touches
3 conflicts
0x3793b011…d280
0x34b655…2a6f
4 touches
1 conflict
0x601b8bfa…e255
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
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
10 conflicts on slot 0xdacb24f781…a756ce
Audit this contract →
← previous block·next block →recent activity