← previous blocknext block →recent activity
Analyzing
Block #90,820,423
56 transactions · 42 stateful · 2026-07-27 16:33:37 UTC
Parallelism
82/100
Blocked
60%
Avg conflicts / tx
1.27
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #90,820,423 · 56 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w08w110w115w016w117w219w320w423w032w435w539w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
10 touches
10 conflicts
0x00000000…004b
0x80c745…7210
10 touches
10 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0x3533c73a…e8f0
0xd32edf…ff58
7 touches
6 conflicts
0x4cabb80a…46bf
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity