← previous blocknext block →recent activity
Analyzing
Block #95,395,528
15 transactions · 14 stateful · 2026-08-12 16:42:02 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,395,528 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w17w210w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
8 touches
6 conflicts
0xfd94e24a…9278
0x851145…3f07
4 touches
1 conflict
0x4615a47d…1c43
0x34b655…2a6f
4 touches
1 conflict
0x4615a47d…1c44
0x34b655…2a6f
4 touches
1 conflict
0x511cdf65…47ab
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x8900cf87…5261
0x34b655…2a6f
4 touches
1 conflict
0xf073c0d9…584e
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
6 conflicts on slot 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity