← previous blocknext block →recent activity
Analyzing
Block #95,034,096
15 transactions · 14 stateful · 2026-08-11 10:10:51 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,034,096 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xe05789d9…2376
0x968279…9342
4 touches
1 conflict
0x9a2a0532…f8b1
0x968279…9342
4 touches
1 conflict
0x9a2a0532…f8b3
0x968279…9342
4 touches
1 conflict
0xe05789d9…236f
0x968279…9342
4 touches
1 conflict
0xe05789d9…2370
0x968279…9342
4 touches
1 conflict
0xe05789d9…2373
0x968279…9342
4 touches
1 conflict
0xe05789d9…2374
0x968279…9342
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: USDC (USDC)
3 conflicts on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity