← previous blocknext block →recent activity
Analyzing
Block #95,128,388
18 transactions · 14 stateful · 2026-08-11 18:05:36 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,128,388 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w311w412w517w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
12 touches
15 conflicts
0x390dd46c…deef
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f4a7ac3…021c
0x34b655…2a6f
4 touches
1 conflict
0x536588d3…19c5
0x34b655…2a6f
4 touches
1 conflict
0x5d2e788d…5867
0x34b655…2a6f
4 touches
1 conflict
0x83dea465…8a72
0x34b655…2a6f
4 touches
1 conflict
0x90d127f4…5c92
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
15 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity