← previous blocknext block →recent activity
Analyzing
Block #91,268,749
18 transactions · 17 stateful · 2026-07-29 06:10:10 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,268,749 · 18 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
1w06w07w19w110w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91e51cb…d65c
0x7b9256…1fb2
4 touches
1 conflict
0xa91e51cb…d65a
0x7b9256…1fb2
4 touches
1 conflict
0xa91e51cb…d65b
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x4102cb2a…3b17
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 0xa91e51cb31…b9d65c
Audit this contract →
← previous block·next block →recent activity