← previous blocknext block →recent activity
Analyzing
Block #90,221,551
8 transactions · 6 stateful · 2026-07-25 14:05:44 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,221,551 · 8 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
0xeea96826…b11e
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe867820f…154c
0x34b655…2a6f
4 touches
1 conflict
0x0be4c4cd…c261
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x0fb9e50c…1a35
0x34b655…2a6f
2 touches
0 conflicts
0x1c3295fd…097a
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 0xeea96826b6…ecb11e
Audit this contract →
← previous block·next block →recent activity