← previous blocknext block →recent activity
Analyzing
Block #112,350,636
32 transactions · 25 stateful · 2026-10-11 02:34:47 UTC
Parallelism
84/100
Blocked
40%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,350,636 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w19w010w114w218w020w121w322w023w124w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x134d29ed…64c5
0x508254…98bd
10 touches
10 conflicts
0xe1c4d8e8…ffa8
0x508254…98bd
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x3a663e9a…a9c4
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c5
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c6
0x508254…98bd
8 touches
6 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c8
0x508254…98bd
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: 0x508254c8…4a98bd
10 conflicts on slot 0x134d29ed5c…4664c5
Audit this contract →
← previous block·next block →recent activity