← previous blocknext block →recent activity
Analyzing
Block #90,574,928
10 transactions · 9 stateful · 2026-07-26 19:58:29 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,574,928 · 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
4w05w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80d4d75a…ca3d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x21852c6f…fd6f
0x34b655…2a6f
4 touches
1 conflict
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x20162f0b…e877
0x34b655…2a6f
2 touches
0 conflicts
0x2a49f3bf…713b
0x34b655…2a6f
2 touches
0 conflicts
0x2fc30b22…e3ad
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
1 conflict on slot 0x80d4d75af1…91ca3d
Audit this contract →
← previous block·next block →recent activity