← previous blocknext block →recent activity
Analyzing
Block #95,276,172
20 transactions · 20 stateful · 2026-08-12 06:37:50 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,276,172 · 20 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
5w06w17w08w09w110w211w312w415w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccf7ccc2…bf2d
0x968279…9342
10 touches
10 conflicts
0xccf7ccc2…bf30
0x968279…9342
10 touches
10 conflicts
0xd2bfdf9c…9e78
0x968279…9342
10 touches
10 conflicts
0xd2bfdf9c…9e79
0x968279…9342
10 touches
10 conflicts
0xd2bfdf9c…9e7f
0x968279…9342
10 touches
10 conflicts
0xd2bfdf9c…9e7d
0x968279…9342
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
0x521a5982…a82a
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 0xccf7ccc2d6…b0bf2d
Audit this contract →
← previous block·next block →recent activity