← previous blocknext block →recent activity
Analyzing
Block #112,418,607
13 transactions · 13 stateful · 2026-10-11 08:16:44 UTC
Parallelism
46/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,418,607 · 13 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
1w02w15w26w37w38w49w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x9d1c9a2f…4431
0x34b655…2a6f
4 touches
1 conflict
0xac7747f6…0550
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xcd4b2ad1…21fa
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