← previous blocknext block →recent activity
Analyzing
Block #90,688,756
18 transactions · 17 stateful · 2026-07-27 05:31:08 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,688,756 · 18 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
1w02w13w24w35w06w08w110w111w212w313w414w515w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x948836ff…59ab
0x34b655…2a6f
10 touches
10 conflicts
0xa913c76e…06d8
0xd32edf…ff58
7 touches
6 conflicts
0xa73a07e4…b066
0x34b655…2a6f
6 touches
4 conflicts
0x52543a50…9020
0x34b655…2a6f
6 touches
3 conflicts
0x33f25af8…96ee
0x34b655…2a6f
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity