← previous blocknext block →recent activity
Analyzing
Block #112,492,851
21 transactions · 19 stateful · 2026-10-11 14:30:18 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,492,851 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w19w010w112w113w214w315w416w417w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c0247e1…a87b
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0xdad20621…06b1
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x17a7f697…dcb5
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x7954ece9…fef0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
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 0x4c0247e12c…f6a87b
Audit this contract →
← previous block·next block →recent activity