← previous blocknext block →recent activity

Analyzing

Block #85,714,065

36 transactions · 19 stateful · 2026-07-05 07:19:13 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.86

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,714,065  ·  36 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

0x663f3711…842c

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

2 touches
0 conflicts

0x7d42dc8b…fdb6

0x2a68ba…90c5

2 touches
0 conflicts

0xd025d7d7…f05a

0x3bd359…433a

2 touches
0 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

2 touches
0 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

28 conflicts on slot 0x663f37117d…df842c

← previous block·next block →recent activity