← previous blocknext block →recent activity

Analyzing

Block #86,682,419

44 transactions · 37 stateful · 2026-07-09 19:05:29 UTC

Parallelism

75/100

Blocked

73%

Avg conflicts / tx

1.77

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #86,682,419  ·  44 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xbdfbf751…c8e5

0xd32edf…ff58

17 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a9

0xb1dbf0…c0d3

8 touches
6 conflicts

0x00000000…0002

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

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 0xbdfbf751f9…1ec8e5

← previous block·next block →recent activity