← previous blocknext block →recent activity
Analyzing
Block #112,585,507
17 transactions · 17 stateful · 2026-10-11 22:16:29 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,585,507 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w29w010w111w112w213w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36890fff…f3d1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x4979282b…2937
0x1b6862…e19c
6 touches
3 conflicts
0x6dfa1a0f…aeec
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xbea0c6d8…42cd
0xd32edf…ff58
5 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
3 conflicts on slot 0x36890fff7e…d7f3d1
Audit this contract →
← previous block·next block →recent activity