← previous blocknext block →recent activity

Analyzing

Block #86,298,456

41 transactions · 32 stateful · 2026-07-08 00:17:02 UTC

Parallelism

71/100

Blocked

63%

Avg conflicts / tx

2.07

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #86,298,456  ·  41 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

0x75f33fb9…2ed0

0xd32edf…ff58

23 touches
66 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x01cab646…0800

0x34b655…2a6f

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

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

66 conflicts on slot 0x75f33fb910…1d2ed0

← previous block·next block →recent activity