← previous blocknext block →recent activity
Analyzing
Block #112,557,506
16 transactions · 16 stateful · 2026-10-11 19:55:37 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,557,506 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w19w210w211w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x708d7a74…09e3
0x34b655…2a6f
8 touches
6 conflicts
0x7229e25b…d99e
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0x0ffee004…5595
0x34b655…2a6f
6 touches
3 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x46c4d22b…e932
0x34b655…2a6f
4 touches
1 conflict
0x505a313c…397f
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 0xe720a4c698…508eb0
Audit this contract →
← previous block·next block →recent activity