← previous blocknext block →recent activity
Analyzing
Block #90,821,269
23 transactions · 22 stateful · 2026-07-27 16:37:53 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,821,269 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w08w19w010w111w212w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1f7a235…9483
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x3e0065ad…e39b
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
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
6 conflicts on slot 0xa1f7a235c3…789483
Audit this contract →
← previous block·next block →recent activity