← previous blocknext block →recent activity

Analyzing

Block #85,910,191

28 transactions · 23 stateful · 2026-07-06 05:05:17 UTC

Parallelism

75/100

Blocked

57%

Avg conflicts / tx

1.07

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,910,191  ·  28 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xfb6857ce…579a

0xd32edf…ff58

11 touches
15 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

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: FastLane: FastLaneAuctionHandler

15 conflicts on slot 0xfb6857ce7e…66579a

← previous block·next block →recent activity