← previous blocknext block →recent activity
Analyzing
Block #90,851,651
64 transactions · 40 stateful · 2026-07-27 19:10:42 UTC
Parallelism
83/100
Blocked
65%
Avg conflicts / tx
1.33
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #90,851,651 · 64 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
1w02w13w24w35w16w27w315w016w117w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xde9d38a8…4c0f
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x0f7df08f…cad4
0xa6afd3…d132
8 touches
6 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity