← previous blocknext block →recent activity
Analyzing
Block #90,790,979
22 transactions · 21 stateful · 2026-07-27 14:05:24 UTC
Parallelism
73/100
Blocked
67%
Avg conflicts / tx
1.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,790,979 · 22 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
1w03w04w15w16w27w38w49w111w312w213w415w517w218w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x379dc435…6616
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x3a37aad1…720f
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4f394483…ff62
0x34b655…2a6f
8 touches
6 conflicts
0xf6ac2366…aa27
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x379dc43545…336616
Audit this contract →
← previous block·next block →recent activity