← previous blocknext block →recent activity
Analyzing
Block #90,867,625
14 transactions · 14 stateful · 2026-07-27 20:31:07 UTC
Parallelism
50/100
Blocked
64%
Avg conflicts / tx
1.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,867,625 · 14 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
1w02w13w24w35w46w57w58w612w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe2e52e46…0894
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
8 touches
6 conflicts
0x5c02a8ab…13c6
0x34b655…2a6f
7 touches
6 conflicts
0xfcfb570f…cf1c
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity