← previous blocknext block →recent activity
Analyzing
Block #95,751,044
14 transactions · 13 stateful · 2026-08-13 22:32:05 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,751,044 · 14 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
5w06w17w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36565e7…6d49
0x968279…9342
10 touches
10 conflicts
0x521a5982…a82a
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x968279…9342
10 touches
10 conflicts
0xaaeef6e3…015f
0x968279…9342
10 touches
10 conflicts
0xaaeef6e3…0160
0x968279…9342
10 touches
10 conflicts
0xaaeef6e3…0162
0x968279…9342
10 touches
10 conflicts
0xc36565e7…6d42
0x968279…9342
10 touches
10 conflicts
0xc36565e7…6d43
0x968279…9342
10 touches
10 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
10 conflicts on slot 0xc36565e74d…d66d49
Audit this contract →
← previous block·next block →recent activity