← previous blocknext block →recent activity
Analyzing
Block #95,079,328
21 transactions · 21 stateful · 2026-08-11 13:58:49 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,079,328 · 21 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
1w02w03w04w16w07w19w010w111w212w313w017w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe50364fa…7edb
0x968279…9342
8 touches
6 conflicts
0x4519cdbd…1d5d
0x968279…9342
8 touches
6 conflicts
0x4519cdbd…1d60
0x968279…9342
8 touches
6 conflicts
0x4519cdbd…1d61
0x968279…9342
8 touches
6 conflicts
0x4519cdbd…1d63
0x968279…9342
8 touches
6 conflicts
0xe50364fa…7ed8
0x968279…9342
8 touches
6 conflicts
0xe50364fa…7ed9
0x968279…9342
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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: 0x96827978…f09342
6 conflicts on slot 0xe50364fae6…db7edb
Audit this contract →
← previous block·next block →recent activity