← previous blocknext block →recent activity
Analyzing
Block #95,572,928
15 transactions · 13 stateful · 2026-08-13 07:35:08 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,572,928 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8c3f355…5953
0x968279…9342
6 touches
3 conflicts
0xe8c3f355…5956
0x968279…9342
6 touches
3 conflicts
0xe8c3f355…5957
0x968279…9342
6 touches
3 conflicts
0xe8c3f355…5958
0x968279…9342
6 touches
3 conflicts
0xb0a95e37…470a
0x968279…9342
6 touches
3 conflicts
0xb0a95e37…470c
0x968279…9342
6 touches
3 conflicts
0xe8c3f355…5952
0x968279…9342
6 touches
3 conflicts
0xc824469a…6425
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: 0x96827978…f09342
3 conflicts on slot 0xe8c3f35599…e75953
Audit this contract →
← previous block·next block →recent activity