← previous blocknext block →recent activity

Analyzing

Block #85,160,901

23 transactions · 22 stateful · 2026-07-02 17:54:06 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

0.96

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,160,901  ·  23 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

0x39c35deb…aa9a

0xd32edf…ff58

11 touches
15 conflicts

0x2886e2bc…6ab8

0x065c9d…c394

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

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

0x2b093939…9085

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 0x39c35deb08…b2aa9a

← previous block·next block →recent activity