← previous blocknext block →recent activity
Analyzing
Block #95,625,214
14 transactions · 13 stateful · 2026-08-13 11:58:08 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,625,214 · 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
7w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f50700b…0d65
0x968279…9342
10 touches
10 conflicts
0x2f50700b…0d66
0x968279…9342
10 touches
10 conflicts
0x2f50700b…0d68
0x968279…9342
10 touches
10 conflicts
0x5026f3d8…2505
0x968279…9342
10 touches
10 conflicts
0x5026f3d8…2506
0x968279…9342
10 touches
10 conflicts
0x5026f3d8…2508
0x968279…9342
10 touches
10 conflicts
0x521a5982…a82a
0x754704…b603
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
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 0x2f50700b4a…6e0d65
Audit this contract →
← previous block·next block →recent activity