← previous blocknext block →recent activity
Analyzing
Block #91,152,075
9 transactions · 9 stateful · 2026-07-28 20:23:01 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,152,075 · 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
2w03w14w05w16w07w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58b47a58…586e
0x7b9256…1fb2
4 touches
1 conflict
0x58b47a58…586f
0x7b9256…1fb2
4 touches
1 conflict
0x58b47a58…5872
0x7b9256…1fb2
4 touches
1 conflict
0xf5cd7d49…fedf
0x7b9256…1fb2
4 touches
1 conflict
0xf5cd7d49…fee0
0x7b9256…1fb2
4 touches
1 conflict
0x5fe7e126…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x802738ef…9072
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 0x58b47a58d0…d7586e
Audit this contract →
← previous block·next block →recent activity