← previous blocknext block →recent activity
Analyzing
Block #90,557,813
13 transactions · 13 stateful · 2026-07-26 18:32:24 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,557,813 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w211w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3cd0632…be7d
0x34b655…2a6f
4 touches
1 conflict
0xac62ede4…57c0
0x34b655…2a6f
4 touches
1 conflict
0xac62ede4…57c1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x088adada…2aa2
0x34b655…2a6f
4 touches
1 conflict
0x08aa7012…a05b
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
1 conflict on slot 0xf3cd063224…c7be7d
Audit this contract →
← previous block·next block →recent activity