← previous blocknext block →recent activity
Analyzing
Block #90,621,610
16 transactions · 16 stateful · 2026-07-26 23:53:21 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,621,610 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w38w09w410w511w612w214w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e58f1d6…2fca
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xf6ce7ec5…9968
0x34b655…2a6f
8 touches
6 conflicts
0x66b62dc6…1554
0x34b655…2a6f
8 touches
6 conflicts
0x65398157…785c
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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 0x4e58f1d685…d82fca
Audit this contract →
← previous block·next block →recent activity