← previous blocknext block →recent activity
Analyzing
Block #112,594,610
24 transactions · 19 stateful · 2026-10-11 23:02:17 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #112,594,610 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w117w018w119w120w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51e4914b…606f
0x34b655…2a6f
6 touches
3 conflicts
0x27034002…2f27
0x34b655…2a6f
6 touches
3 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
6 touches
3 conflicts
0xccec40b5…9e85
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x7cf55485…1681
0x34b655…2a6f
4 touches
1 conflict
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
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
3 conflicts on slot 0x51e4914bf3…b0606f
Audit this contract →
← previous block·next block →recent activity