← previous blocknext block →recent activity
Analyzing
Block #90,530,138
16 transactions · 15 stateful · 2026-07-26 16:13:11 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,530,138 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w37w49w110w511w212w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e737223…2278
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xabffe139…e172
0x34b655…2a6f
8 touches
6 conflicts
0x8743e1ba…8331
0x34b655…2a6f
8 touches
6 conflicts
0x89678d1b…463e
0xa6afd3…d132
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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 0x1e737223a3…202278
Audit this contract →
← previous block·next block →recent activity