← previous blocknext block →recent activity
Analyzing
Block #112,580,756
14 transactions · 13 stateful · 2026-10-11 21:52:35 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,580,756 · 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
6w08w19w010w211w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33649c4f…b327
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0x6df1d50f…8a92
0x34b655…2a6f
4 touches
1 conflict
0x4d72a0b2…87ee
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
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
3 conflicts on slot 0x33649c4f08…eeb327
Audit this contract →
← previous block·next block →recent activity