← previous blocknext block →recent activity
Analyzing
Block #90,324,025
11 transactions · 10 stateful · 2026-07-25 22:44:28 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,324,025 · 11 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
1w02w13w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x34724223…fd0f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xadd2210b…9e29
0x34b655…2a6f
4 touches
1 conflict
0x0d1e7460…1cfa
0x34b655…2a6f
2 touches
0 conflicts
0x1eb0fab5…3517
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity