← previous blocknext block →recent activity
Analyzing
Block #90,039,891
10 transactions · 10 stateful · 2026-07-24 22:47:15 UTC
Parallelism
30/100
Blocked
70%
Avg conflicts / tx
1.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,039,891 · 10 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
1w02w13w24w35w36w48w59w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x453a271e…8768
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf2d8abfb…9cb6
0x34b655…2a6f
6 touches
3 conflicts
0x6aea3f64…bb1f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd6
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd7
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
6 conflicts on slot 0x453a271e0d…c58768
Audit this contract →
← previous block·next block →recent activity