← previous blocknext block →recent activity
Analyzing
Block #112,379,550
20 transactions · 18 stateful · 2026-10-11 05:00:14 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,379,550 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w011w012w113w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7954ece9…fef0
0x34b655…2a6f
10 touches
10 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xb8023787…61f9
0x34b655…2a6f
6 touches
3 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xb3391128…ab1e
0x34b655…2a6f
4 touches
1 conflict
0x9d1c9a2f…4431
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 0x7954ece9af…e7fef0
Audit this contract →
← previous block·next block →recent activity