← previous blocknext block →recent activity

Analyzing

Block #85,991,304

22 transactions · 20 stateful · 2026-07-06 14:06:29 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.09

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,991,304  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xdb5c308d…759f

0xd32edf…ff58

11 touches
15 conflicts

0xa4f80979…4d71

0x065c9d…c394

6 touches
3 conflicts

0x2c506459…5351

0x34b655…2a6f

6 touches
3 conflicts

0x59645a97…3ca1

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

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 0xdb5c308df9…3e759f

← previous block·next block →recent activity