← previous blocknext block →recent activity
Analyzing
Block #95,654,251
19 transactions · 18 stateful · 2026-08-13 14:24:12 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,654,251 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w010w111w212w313w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ae2cb31…d10d
0x968279…9342
8 touches
6 conflicts
0xaac88174…bf52
0x968279…9342
8 touches
6 conflicts
0xaac88174…bf53
0x968279…9342
8 touches
6 conflicts
0xaac88174…bf55
0x968279…9342
8 touches
6 conflicts
0x6ae2cb31…d107
0x968279…9342
8 touches
6 conflicts
0x6ae2cb31…d10a
0x968279…9342
8 touches
6 conflicts
0x6ae2cb31…d10b
0x968279…9342
8 touches
6 conflicts
0xbcbf5d09…8bac
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 0x6ae2cb317f…47d10d
Audit this contract →
← previous block·next block →recent activity