← previous blocknext block →recent activity
Analyzing
Block #112,236,426
20 transactions · 16 stateful · 2026-10-10 17:00:10 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,236,426 · 20 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
3w07w19w210w311w112w213w314w417w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8afce1b6…3ce0
0x34b655…2a6f
8 touches
6 conflicts
0x10ffbe67…41c1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x05522dbb…36dc
0x34b655…2a6f
4 touches
1 conflict
0x27145bc1…96cc
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 0x8afce1b6a3…ae3ce0
Audit this contract →
← previous block·next block →recent activity