← previous blocknext block →recent activity
Analyzing
Block #95,596,251
20 transactions · 19 stateful · 2026-08-13 09:32:27 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,596,251 · 20 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
1w05w06w17w28w39w010w111w212w313w414w515w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8b48e27…23a6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x6a0c619a…b189
0x34b655…2a6f
6 touches
4 conflicts
0xe3684e08…c96a
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
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: Perpl
10 conflicts on slot 0xd8b48e27ad…6f23a6
Audit this contract →
← previous block·next block →recent activity