← previous blocknext block →recent activity
Analyzing
Block #95,714,522
14 transactions · 13 stateful · 2026-08-13 19:28:20 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,714,522 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w06w18w211w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x280bd9bd…f01d
0x34b655…2a6f
6 touches
3 conflicts
0x3c8d99a5…b937
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x320701d5…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
0x34b655…2a6f
4 touches
1 conflict
0x3d2c514e…49b1
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
3 conflicts on slot 0x280bd9bd22…2ef01d
Audit this contract →
← previous block·next block →recent activity