← previous blocknext block →recent activity
Analyzing
Block #90,850,828
34 transactions · 32 stateful · 2026-07-27 19:06:34 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,850,828 · 34 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
1w02w03w110w011w112w213w114w115w220w221w323w024w128w031w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4685e49e…77c6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x38b5b2ce…c5bb
0xfa32f9…f3f0
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 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
6 conflicts on slot 0x4685e49e98…8f77c6
Audit this contract →
← previous block·next block →recent activity