← previous blocknext block →recent activity
Analyzing
Block #112,523,281
24 transactions · 20 stateful · 2026-10-11 17:03:24 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,523,281 · 24 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
1w02w03w16w08w09w115w117w018w119w220w321w022w223w3
- 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
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x62023181…811e
0x34b655…2a6f
6 touches
3 conflicts
0xe22c1d6f…b586
0x508254…98bd
4 touches
1 conflict
0xe22c1d6f…b588
0x508254…98bd
4 touches
1 conflict
0xe22c1d6f…b58d
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