← previous blocknext block →recent activity
Analyzing
Block #90,531,091
13 transactions · 13 stateful · 2026-07-26 16:17:59 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
0.77
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,531,091 · 13 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
1w02w14w05w16w27w29w010w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc46dfd53…3305
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x103be197…826c
0xa6afd3…d132
6 touches
3 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
6 touches
3 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
6 touches
3 conflicts
0x27754bd4…96ae
0x34b655…2a6f
6 touches
3 conflicts
0x34933aba…06e4
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 0xc46dfd534a…523305
Audit this contract →
← previous block·next block →recent activity