← previous blocknext block →recent activity
Analyzing
Block #91,385,933
15 transactions · 12 stateful · 2026-07-29 16:00:30 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,385,933 · 15 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
2w05w07w08w110w211w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd81dbbb9…d0c5
0x34b655…2a6f
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xeae9315c…7835
0x065c9d…c394
5 touches
3 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0x877afa22…df14
0x40c49f…2af0
2 touches
0 conflicts
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: Perpl
3 conflicts on slot 0xd81dbbb94a…7dd0c5
Audit this contract →
← previous block·next block →recent activity