← previous blocknext block →recent activity
Analyzing
Block #91,975,050
14 transactions · 14 stateful · 2026-07-31 17:25:26 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,975,050 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6768f2b5…39ee
0x7b9256…1fb2
6 touches
3 conflicts
0x6768f2b5…39f1
0x7b9256…1fb2
6 touches
3 conflicts
0x678d395d…7683
0x7b9256…1fb2
6 touches
3 conflicts
0x678d395d…7684
0x7b9256…1fb2
6 touches
3 conflicts
0x678d395d…7685
0x7b9256…1fb2
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x6768f2b5…39ed
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
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: 0x7b9256fd…e21fb2
3 conflicts on slot 0x6768f2b550…1b39ee
Audit this contract →
← previous block·next block →recent activity