← previous blocknext block →recent activity
Analyzing
Block #95,977,611
20 transactions · 18 stateful · 2026-08-14 17:31:59 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,977,611 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w18w09w110w211w312w413w514w015w116w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc363ff23…e97e
0x968279…9342
12 touches
15 conflicts
0x521a5982…a82a
0x754704…b603
12 touches
15 conflicts
0x00000000…0006
0x968279…9342
12 touches
15 conflicts
0x8810142b…5fec
0x968279…9342
12 touches
15 conflicts
0x8810142b…5fed
0x968279…9342
12 touches
15 conflicts
0x8810142b…5fef
0x968279…9342
12 touches
15 conflicts
0xc363ff23…e977
0x968279…9342
12 touches
15 conflicts
0xc363ff23…e978
0x968279…9342
12 touches
15 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
15 conflicts on slot 0xc363ff23d0…76e97e
Audit this contract →
← previous block·next block →recent activity