← previous blocknext block →recent activity
Analyzing
Block #95,128,475
17 transactions · 16 stateful · 2026-08-11 18:06:03 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,128,475 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w07w18w29w310w411w512w213w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x8ffa3328…ce11
0xe52b14…7230
12 touches
15 conflicts
0x1074cf0a…857b
0xe52b14…7230
10 touches
10 conflicts
0x57070322…bc66
0xe52b14…7230
10 touches
10 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
8 touches
6 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
8 touches
6 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd7
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: 0xe52b1424…bb7230
15 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity