← previous blocknext block →recent activity
Analyzing
Block #91,079,063
9 transactions · 9 stateful · 2026-07-28 14:15:39 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,079,063 · 9 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
1w02w13w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e370792…a916
0x7b9256…1fb2
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x5891d42e…580b
0x7b9256…1fb2
4 touches
1 conflict
0x5891d42e…580c
0x7b9256…1fb2
4 touches
1 conflict
0x5891d42e…580f
0x7b9256…1fb2
4 touches
1 conflict
0x5e370792…a915
0x7b9256…1fb2
4 touches
1 conflict
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
1 conflict on slot 0x5e3707927c…72a916
Audit this contract →
← previous block·next block →recent activity