← previous blocknext block →recent activity
Analyzing
Block #95,278,641
46 transactions · 45 stateful · 2026-08-12 06:50:15 UTC
Parallelism
96/100
Blocked
4%
Avg conflicts / tx
0.04
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,278,641 · 46 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w041w142w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83a3f833…8268
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
2 touches
0 conflicts
0x3cb4257f…b98c
0x34b655…2a6f
2 touches
0 conflicts
0x3cb4257f…b98d
0x34b655…2a6f
2 touches
0 conflicts
0x4a2afb00…a2a8
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
1 conflict on slot 0x83a3f83355…d28268
Audit this contract →
← previous block·next block →recent activity