← previous blocknext block →recent activity
Analyzing
Block #90,544,086
10 transactions · 9 stateful · 2026-07-26 17:23:21 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,544,086 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x9f889f59…5c45
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0ade614b…96fc
0x065c9d…c394
2 touches
0 conflicts
0x1c2ef827…7d44
0x065c9d…c394
2 touches
0 conflicts
0x3b70b287…1424
0x065c9d…c394
2 touches
0 conflicts
0xdca12a0d…827f
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
1 conflict on slot 0xf51ec09cc1…a1b4a9
Audit this contract →
← previous block·next block →recent activity