← previous blocknext block →recent activity
Analyzing
Block #95,578,843
20 transactions · 19 stateful · 2026-08-13 08:04:53 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,578,843 · 20 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
3w04w15w06w17w08w19w210w011w313w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4616ceb…2177
0x968279…9342
6 touches
3 conflicts
0xc4722f12…3a09
0x968279…9342
6 touches
3 conflicts
0xc4722f12…3a0a
0x968279…9342
6 touches
3 conflicts
0xc4722f12…3a0c
0x968279…9342
6 touches
3 conflicts
0xd4616ceb…2171
0x968279…9342
6 touches
3 conflicts
0xd4616ceb…2172
0x968279…9342
6 touches
3 conflicts
0xd4616ceb…2175
0x968279…9342
6 touches
3 conflicts
0xd4616ceb…2176
0x968279…9342
6 touches
3 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
3 conflicts on slot 0xd4616ceb8c…542177
Audit this contract →
← previous block·next block →recent activity