← previous blocknext block →recent activity
Analyzing
Block #90,794,601
48 transactions · 41 stateful · 2026-07-27 14:23:37 UTC
Parallelism
71/100
Blocked
66%
Avg conflicts / tx
1.69
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #90,794,601 · 48 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w29w010w111w315w019w120w221w022w123w224w325w426w527w629w631w735w236w838w340w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x671560e4…1c4f
0x34b655…2a6f
10 touches
10 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
8 touches
6 conflicts
0xe9452241…95a3
0x34b655…2a6f
8 touches
6 conflicts
0xebc6cc8e…c0a7
0xd32edf…ff58
7 touches
6 conflicts
0x24eaf46d…8c2e
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity