← previous blocknext block →recent activity
Analyzing
Block #90,630,056
20 transactions · 16 stateful · 2026-07-27 00:35:50 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,630,056 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w27w38w112w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1c1e591b…d93d
0x34b655…2a6f
4 touches
1 conflict
0x1e54f03a…b21b
0x34b655…2a6f
4 touches
1 conflict
0x3714402e…1c25
0x34b655…2a6f
4 touches
1 conflict
0x3dee5964…2c31
0x34b655…2a6f
4 touches
1 conflict
0x474ccab4…b3cc
0x34b655…2a6f
4 touches
1 conflict
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity