← previous blocknext block →recent activity
Analyzing
Block #95,425,088
30 transactions · 27 stateful · 2026-08-12 19:11:32 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,425,088 · 30 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
1w03w14w05w16w27w08w110w314w418w120w021w124w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2b36ab5…39d8
0x34b655…2a6f
10 touches
10 conflicts
0x742436a7…c4d4
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
6 touches
3 conflicts
0x442e26a3…e968
0x34b655…2a6f
6 touches
3 conflicts
0xefe44fc9…83c3
0x851145…3f07
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
10 conflicts on slot 0xf2b36ab561…2e39d8
Audit this contract →
← previous block·next block →recent activity