← previous blocknext block →recent activity
Analyzing
Block #90,696,930
23 transactions · 20 stateful · 2026-07-27 06:12:15 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,696,930 · 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
1w02w15w08w19w212w013w114w315w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9db3090e…7fb8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x56a3cfae…8879
0x34b655…2a6f
4 touches
1 conflict
0x587de2e8…162e
0x34b655…2a6f
4 touches
1 conflict
0x68a9868a…6c27
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x6e859a7c…d0f2
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 0x9db3090ea3…da7fb8
Audit this contract →
← previous block·next block →recent activity