← previous blocknext block →recent activity
Analyzing
Block #91,402,936
16 transactions · 14 stateful · 2026-07-29 17:26:05 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,402,936 · 16 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
4w05w18w29w310w411w513w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7fafeda…dff1
0x34b655…2a6f
6 touches
3 conflicts
0xefcdf197…96a2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x409d9cb9…36a8
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
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: Perpl
3 conflicts on slot 0xb7fafedaa2…86dff1
Audit this contract →
← previous block·next block →recent activity