← previous blocknext block →recent activity
Analyzing
Block #90,893,434
40 transactions · 32 stateful · 2026-07-27 22:40:56 UTC
Parallelism
73/100
Blocked
59%
Avg conflicts / tx
1.55
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #90,893,434 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w16w010w114w015w116w217w318w419w520w621w722w826w227w330w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x103be197…826c
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x745952b2…d90c
0x34b655…2a6f
6 touches
3 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity