← previous blocknext block →recent activity
Analyzing
Block #90,791,616
24 transactions · 23 stateful · 2026-07-27 14:08:36 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,791,616 · 24 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
1w02w13w24w15w06w18w010w111w212w313w414w115w217w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x007892de…5752
0x34b655…2a6f
8 touches
6 conflicts
0xb2022d4d…0ca0
0xa6afd3…d132
6 touches
3 conflicts
0x6713b018…05f3
0x34b655…2a6f
6 touches
3 conflicts
0x1c6b666d…4943
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xf54adf24…263f
0xd32edf…ff58
5 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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity