← previous blocknext block →recent activity
Analyzing
Block #112,484,793
20 transactions · 19 stateful · 2026-10-11 13:49:45 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,484,793 · 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
6w07w09w110w011w112w213w314w315w416w517w618w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x931975c2…b7b3
0x34b655…2a6f
8 touches
6 conflicts
0xdad20621…06b1
0x34b655…2a6f
8 touches
6 conflicts
0x53057a6c…ce62
0x34b655…2a6f
6 touches
3 conflicts
0x6ac4a9ce…5f63
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa57576bb…e01f
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 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity