← previous blocknext block →recent activity
Analyzing
Block #95,286,684
23 transactions · 20 stateful · 2026-08-12 07:30:44 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,286,684 · 23 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
1w02w13w24w37w111w012w113w214w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x50163ce5…03e0
0xd32edf…ff58
7 touches
6 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0xb371802a…310c
0x34b655…2a6f
5 touches
3 conflicts
0x7c709217…21b4
0x34b655…2a6f
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity