← previous blocknext block →recent activity
Analyzing
Block #95,564,858
16 transactions · 15 stateful · 2026-08-13 06:54:33 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,564,858 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcee3ff5…c6d6
0x968279…9342
8 touches
6 conflicts
0xdcee3ff5…c6d7
0x968279…9342
8 touches
6 conflicts
0xdcee3ff5…c6d8
0x968279…9342
8 touches
6 conflicts
0x8daff965…05c9
0x968279…9342
8 touches
6 conflicts
0x8daff965…05ca
0x968279…9342
8 touches
6 conflicts
0x8daff965…05cc
0x968279…9342
8 touches
6 conflicts
0xdcee3ff5…c6d2
0x968279…9342
8 touches
6 conflicts
0xdcee3ff5…c6d3
0x968279…9342
8 touches
6 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
6 conflicts on slot 0xdcee3ff537…bec6d6
Audit this contract →
← previous block·next block →recent activity