← previous blocknext block →recent activity
Analyzing
Block #112,505,636
29 transactions · 24 stateful · 2026-10-11 15:34:37 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,505,636 · 29 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
1w03w14w08w112w013w114w116w017w120w021w122w223w324w025w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22c1d6f…b5c7
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c6
0x508254…98bd
8 touches
6 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
8 touches
6 conflicts
0x08cfec9d…7ef0
0x508254…98bd
8 touches
6 conflicts
0xe1c4d8e8…ffa8
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0x08cfec9d…7ee3
0x508254…98bd
4 touches
1 conflict
0x08cfec9d…7ee8
0x508254…98bd
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: 0x508254c8…4a98bd
6 conflicts on slot 0xe22c1d6f16…97b5c7
Audit this contract →
← previous block·next block →recent activity