← previous blocknext block →recent activity
Analyzing
Block #112,594,074
24 transactions · 23 stateful · 2026-10-11 22:59:35 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,594,074 · 24 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
10w011w113w014w115w116w217w318w419w420w521w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x502392cc…4265
0x34b655…2a6f
8 touches
6 conflicts
0x85c26c14…ba15
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xde5ddfc2…afb8
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7ed3c39d…3acb
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 0x502392cce2…7c4265
Audit this contract →
← previous block·next block →recent activity