← previous blocknext block →recent activity
Analyzing
Block #91,404,784
26 transactions · 19 stateful · 2026-07-29 17:35:26 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,404,784 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w09w112w213w114w315w416w517w218w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x3e033d91…5255
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0x6eedec62…3ba0
0x065c9d…c394
5 touches
3 conflicts
0x93afca4c…b47e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: Perpl
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity