← previous blocknext block →recent activity
Analyzing
Block #91,255,458
27 transactions · 22 stateful · 2026-07-29 05:03:09 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,255,458 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w211w212w314w117w219w324w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa1ff0729…0146
0xa6afd3…d132
6 touches
3 conflicts
0x890a1db9…1712
0xa6afd3…d132
6 touches
3 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
4 touches
1 conflict
0x3ab1dc16…6f91
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity