← previous blocknext block →recent activity
Analyzing
Block #91,109,866
17 transactions · 15 stateful · 2026-07-28 16:50:40 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,109,866 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w09w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee312d77…1ab4
0x7b9256…1fb2
4 touches
1 conflict
0x4d51e581…1c03
0x7b9256…1fb2
4 touches
1 conflict
0x4d51e581…1c04
0x7b9256…1fb2
4 touches
1 conflict
0x4d51e581…1c07
0x7b9256…1fb2
4 touches
1 conflict
0xee312d77…1ab3
0x7b9256…1fb2
4 touches
1 conflict
0x6aea3f64…bb1f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
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 0xee312d7794…991ab4
Audit this contract →
← previous block·next block →recent activity