← previous blocknext block →recent activity
Analyzing
Block #90,206,258
11 transactions · 7 stateful · 2026-07-25 12:48:42 UTC
Parallelism
64/100
Blocked
57%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,206,258 · 11 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
1w02w13w24w35w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2949065c…60c6
0x34b655…2a6f
2 touches
0 conflicts
0x296231a8…d4f4
0x34b655…2a6f
2 touches
0 conflicts
0x3170337f…16e1
0x34b655…2a6f
2 touches
0 conflicts
0x3eede796…d745
0x34b655…2a6f
2 touches
0 conflicts
0x487aa334…7ef2
0x34b655…2a6f
2 touches
0 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity