← previous blocknext block →recent activity
Analyzing
Block #95,370,245
21 transactions · 19 stateful · 2026-08-12 14:34:00 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,370,245 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w26w07w111w312w313w214w315w416w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd20b4e3…e8d3
0x34b655…2a6f
10 touches
10 conflicts
0xfa0e47ee…2026
0xd32edf…ff58
7 touches
6 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
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 0xbd20b4e389…71e8d3
Audit this contract →
← previous block·next block →recent activity