← previous blocknext block →recent activity
Analyzing
Block #112,522,456
10 transactions · 10 stateful · 2026-10-11 16:59:15 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #112,522,456 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bb8e241…b306
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
4 touches
1 conflict
0x1b4fc04c…7352
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
0x34b655…2a6f
4 touches
1 conflict
0x7ca37471…e35d
0x34b655…2a6f
4 touches
1 conflict
0x52404f3d…4c2e
0x34b655…2a6f
2 touches
0 conflicts
0x91623cd7…dbf4
0x34b655…2a6f
2 touches
0 conflicts
0xaa48195d…ffee
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x8bb8e2413e…b0b306
Audit this contract →
← previous block·next block →recent activity