← previous blocknext block →recent activity
Analyzing
Block #95,173,281
17 transactions · 15 stateful · 2026-08-11 21:51:25 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,173,281 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd4ce93…ae4e
0x34b655…2a6f
4 touches
1 conflict
0x9d1d3633…f0ff
0x34b655…2a6f
4 touches
1 conflict
0xf5899760…c130
0x34b655…2a6f
4 touches
1 conflict
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9f0c
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9f0d
0x16f70c…c3dd
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x217bd767…b79e
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x9fd4ce93a4…99ae4e
Audit this contract →
← previous block·next block →recent activity