← previous blocknext block →recent activity
Analyzing
Block #96,306,318
14 transactions · 13 stateful · 2026-08-15 21:05:28 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,306,318 · 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
6w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bc5e535…9bda
0x968279…9342
10 touches
10 conflicts
0x8bc5e535…9bdb
0x968279…9342
10 touches
10 conflicts
0x8bc5e535…9bdd
0x968279…9342
10 touches
10 conflicts
0xce7fee98…9714
0x968279…9342
10 touches
10 conflicts
0xce7fee98…9715
0x968279…9342
10 touches
10 conflicts
0xce7fee98…9717
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 0x8bc5e53519…3d9bda
Audit this contract →
← previous block·next block →recent activity