← previous blocknext block →recent activity
Analyzing
Block #112,344,601
11 transactions · 10 stateful · 2026-10-11 02:04:25 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,344,601 · 11 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x9d1c9a2f…4431
0x34b655…2a6f
4 touches
1 conflict
0xc8a58694…c63e
0x34b655…2a6f
4 touches
1 conflict
0x5961f9aa…5fe2
0x34b655…2a6f
4 touches
1 conflict
0x8dfe34aa…d62b
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 0x7954ece9af…e7fef0
Audit this contract →
← previous block·next block →recent activity