← previous blocknext block →recent activity
Analyzing
Block #91,086,308
15 transactions · 15 stateful · 2026-07-28 14:52:07 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,086,308 · 15 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
1w02w13w25w06w17w08w09w110w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64f6df54…4259
0x7b9256…1fb2
6 touches
3 conflicts
0x636b0324…945f
0x7b9256…1fb2
6 touches
3 conflicts
0x64f6df54…4258
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x636b0324…945e
0x7b9256…1fb2
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x64f6df540a…da4259
Audit this contract →
← previous block·next block →recent activity