← previous blocknext block →recent activity
Analyzing
Block #90,204,452
7 transactions · 7 stateful · 2026-07-25 12:39:36 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,204,452 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cc65720…396c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x1dd68810…d641
0x34b655…2a6f
2 touches
0 conflicts
0x22c6ecc6…c70d
0x34b655…2a6f
2 touches
0 conflicts
0x3d2f528f…07f9
0x34b655…2a6f
2 touches
0 conflicts
0x487aa334…7ef2
0x34b655…2a6f
2 touches
0 conflicts
0x55cf4758…265c
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 0x0cc657206f…8a396c
Audit this contract →
← previous block·next block →recent activity