← previous blocknext block →recent activity

Analyzing

Block #85,225,516

45 transactions · 35 stateful · 2026-07-03 01:04:24 UTC

Parallelism

73/100

Blocked

63%

Avg conflicts / tx

1.4

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #85,225,516  ·  45 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xf79d837f…fe8f

0xd32edf…ff58

17 touches
36 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…0000

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0003

0x63e48b…53f2

8 touches
6 conflicts

0x00000000…0004

0x63e48b…53f2

8 touches
6 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

8 touches
6 conflicts

0x9a555477…19a8

0x754704…b603

8 touches
6 conflicts

0xd9f18d9a…141d

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

36 conflicts on slot 0xf79d837fb9…44fe8f

← previous block·next block →recent activity