← previous blocknext block →recent activity
Analyzing
Block #95,541,689
33 transactions · 32 stateful · 2026-08-13 04:58:02 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,541,689 · 33 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
3w04w06w17w28w19w026w227w328w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x23df630a…22a5
0x34b655…2a6f
5 touches
3 conflicts
0x39cbc853…9a82
0x34b655…2a6f
4 touches
1 conflict
0x6fd055a9…34a5
0x34b655…2a6f
4 touches
1 conflict
0x9f32f2b3…42d8
0x34b655…2a6f
4 touches
1 conflict
0xbc66586e…20fe
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity