← previous blocknext block →recent activity
Analyzing
Block #90,687,328
16 transactions · 14 stateful · 2026-07-27 05:23:57 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,687,328 · 16 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
3w04w05w19w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0x216a925b…4353
0x34b655…2a6f
4 touches
1 conflict
0x2bcdd4a1…3d3a
0x34b655…2a6f
4 touches
1 conflict
0x30b6b911…e278
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x62593a6d…03d6
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity