← previous blocknext block →recent activity
Analyzing
Block #112,608,884
32 transactions · 28 stateful · 2026-10-12 00:14:06 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,608,884 · 32 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
1w02w13w26w07w08w19w212w121w022w125w128w129w230w331w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa849614b…9faa
0x508254…98bd
8 touches
6 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
8 touches
6 conflicts
0xe1c4d8e8…ffa8
0x508254…98bd
8 touches
6 conflicts
0x3a663e9a…a9c8
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c6
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0xebc2e0d7…958e
0x3bd359…433a
6 touches
3 conflicts
0xb9868b52…c77f
0x34b655…2a6f
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
6 conflicts on slot 0xa849614ba6…279faa
Audit this contract →
← previous block·next block →recent activity