← previous blocknext block →recent activity
Analyzing
Block #90,552,083
21 transactions · 19 stateful · 2026-07-26 18:03:34 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,552,083 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w19w213w315w416w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e7df431…682e
0x34b655…2a6f
8 touches
6 conflicts
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0x92e28bd4…72cc
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3d22c439…de6d
0x34b655…2a6f
6 touches
3 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x1e7df43182…6e682e
Audit this contract →
← previous block·next block →recent activity