← previous blocknext block →recent activity
Analyzing
Block #95,581,969
11 transactions · 11 stateful · 2026-08-13 08:20:37 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,581,969 · 11 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
1w02w15w26w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0xca30efc5…10b3
0x34b655…2a6f
4 touches
1 conflict
0x3f4f9f22…8ad7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x685e7bfd…8856
0x34b655…2a6f
2 touches
0 conflicts
0x6bb86299…6fb4
0x34b655…2a6f
2 touches
0 conflicts
0x6f97afda…faec
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
3 conflicts on slot 0x7be3246e43…72f89f
Audit this contract →
← previous block·next block →recent activity