← previous blocknext block →recent activity
Analyzing
Block #95,807,503
17 transactions · 13 stateful · 2026-08-14 03:16:01 UTC
Parallelism
76/100
Blocked
54%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,807,503 · 17 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
1w02w13w26w17w28w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4efae872…6aa8
0x34b655…2a6f
6 touches
3 conflicts
0xc2b37cdc…e470
0x34b655…2a6f
6 touches
3 conflicts
0x36835e44…04e5
0xd32edf…ff58
5 touches
3 conflicts
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0x93ffcd76…894e
0x34b655…2a6f
4 touches
1 conflict
0x9a9383a9…6bc7
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity