← previous blocknext block →recent activity
Analyzing
Block #85,756,248
40 transactions · 32 stateful · 2026-07-05 11:59:56 UTC
Parallelism
88/100
Blocked
53%
Avg conflicts / tx
1.02
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,756,248 · 40 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w110w011w114w215w316w219w020w121w222w326w229w232w333w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xca0f0668…caf3
0xa6afd3…d132
8 touches
6 conflicts
0xb68e226d…c054
0xa6afd3…d132
8 touches
6 conflicts
0x669d31cf…37e4
0xd32edf…ff58
7 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xa20a130c…5d59
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: Kuru Exchange: Market-WETH/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity