← previous blocknext block →recent activity
Analyzing
Block #95,245,086
23 transactions · 19 stateful · 2026-08-12 03:53:59 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,245,086 · 23 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
2w06w17w18w29w310w311w412w520w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x37d710c8…45c1
0x34b655…2a6f
6 touches
3 conflicts
0xce54c462…7f74
0x34b655…2a6f
6 touches
3 conflicts
0x2794fd34…c82f
0x34b655…2a6f
6 touches
3 conflicts
0x3da7c2bd…1ede
0x34b655…2a6f
6 touches
3 conflicts
0x76c4d722…afa9
0x34b655…2a6f
6 touches
3 conflicts
0x76c4d722…afaa
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity