← previous blocknext block →recent activity
Analyzing
Block #90,794,483
48 transactions · 34 stateful · 2026-07-27 14:23:01 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
2.1
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #90,794,483 · 48 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w08w218w019w120w221w322w423w524w625w726w827w931w1132w135w1240w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x3b1ce1dd…dc2f
0x34b655…2a6f
10 touches
10 conflicts
0xe9452241…95a3
0x34b655…2a6f
8 touches
6 conflicts
0xf3383813…4a0c
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x747f609d…1555
0x34b655…2a6f
6 touches
3 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity