← previous blocknext block →recent activity
Analyzing
Block #95,126,897
18 transactions · 17 stateful · 2026-08-11 17:58:07 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,126,897 · 18 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
1w02w13w26w07w18w311w012w113w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
12 touches
15 conflicts
0xe23d2d79…5112
0x968279…9342
6 touches
3 conflicts
0x4908b926…c7ec
0x968279…9342
6 touches
3 conflicts
0x4908b926…c7ed
0x968279…9342
6 touches
3 conflicts
0x4908b926…c7f0
0x968279…9342
6 touches
3 conflicts
0x4908b926…c7f1
0x968279…9342
6 touches
3 conflicts
0x4908b926…c7f2
0x968279…9342
6 touches
3 conflicts
0xe23d2d79…510f
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: Perpl
15 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity