← previous blocknext block →recent activity
Analyzing
Block #95,195,291
16 transactions · 13 stateful · 2026-08-11 23:42:07 UTC
Parallelism
81/100
Blocked
54%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,195,291 · 16 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
1w02w13w04w16w17w28w09w110w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf50b3c2b…739c
0x968279…9342
6 touches
3 conflicts
0x521a5982…a82a
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0xa2cc282f…142f
0x968279…9342
6 touches
3 conflicts
0xa2cc282f…1430
0x968279…9342
6 touches
3 conflicts
0xa2cc282f…1433
0x968279…9342
6 touches
3 conflicts
0xa2cc282f…1434
0x968279…9342
6 touches
3 conflicts
0xa2cc282f…1435
0x968279…9342
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: 0x96827978…f09342
3 conflicts on slot 0xf50b3c2b26…61739c
Audit this contract →
← previous block·next block →recent activity