← previous blocknext block →recent activity
Analyzing
Block #95,648,879
15 transactions · 14 stateful · 2026-08-13 13:57:10 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,648,879 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda366b17…f884
0x34b655…2a6f
8 touches
6 conflicts
0xbc66586e…20fe
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfe96ad50…3aa3
0x34b655…2a6f
6 touches
3 conflicts
0x78912b00…8f88
0x34b655…2a6f
6 touches
3 conflicts
0x159cff26…7665
0x34b655…2a6f
4 touches
1 conflict
0xe0e00683…e335
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 0xda366b1736…d4f884
Audit this contract →
← previous block·next block →recent activity