← previous blocknext block →recent activity
Analyzing
Block #87,692,321
38 transactions · 35 stateful · 2026-07-14 11:37:33 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,692,321 · 38 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
1w02w13w24w38w09w110w211w312w013w114w215w316w417w530w131w232w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x17c44db3…8888
0xa6afd3…d132
8 touches
6 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0001
0xc1ff9f…b0fc
8 touches
6 conflicts
0xb5a3b1be…8122
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity