← previous blocknext block →recent activity
Analyzing
Block #90,867,327
11 transactions · 10 stateful · 2026-07-27 20:29:37 UTC
Parallelism
28/100
Blocked
70%
Avg conflicts / tx
2.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,867,327 · 11 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
1w02w13w24w35w46w57w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xfb31d278…9107
0x34b655…2a6f
6 touches
3 conflicts
0x70a1ac1f…e2d1
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xb5dab803…6922
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
21 conflicts on slot 0xe2e52e4663…6f0894
Audit this contract →
← previous block·next block →recent activity