← previous blocknext block →recent activity
Analyzing
Block #112,341,424
18 transactions · 18 stateful · 2026-10-11 01:48:26 UTC
Parallelism
61/100
Blocked
39%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,341,424 · 18 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
1w02w13w24w35w36w47w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x9c536ab4…a7de
0x34b655…2a6f
6 touches
3 conflicts
0x295d49d6…e3d1
0x34b655…2a6f
6 touches
3 conflicts
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