← previous blocknext block →recent activity
Analyzing
Block #91,101,297
14 transactions · 12 stateful · 2026-07-28 16:07:34 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,101,297 · 14 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
1w02w13w04w16w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe77be3ae…ffc9
0x7b9256…1fb2
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x88ba3374…0966
0x7b9256…1fb2
4 touches
1 conflict
0x88ba3374…0967
0x7b9256…1fb2
4 touches
1 conflict
0xe77be3ae…ffc5
0x7b9256…1fb2
4 touches
1 conflict
0xe77be3ae…ffc6
0x7b9256…1fb2
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xe77be3ae22…03ffc9
Audit this contract →
← previous block·next block →recent activity