← previous blocknext block →recent activity

Analyzing

Block #86,691,078

34 transactions · 28 stateful · 2026-07-09 20:03:14 UTC

Parallelism

68/100

Blocked

64%

Avg conflicts / tx

2.12

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #86,691,078  ·  34 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

0x6f641e3b…12c3

0xd32edf…ff58

21 touches
55 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x729c91b8…9537

0x188d58…ea8e

6 touches
3 conflicts

0x729c91b8…9538

0x188d58…ea8e

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x745a7fd6…5fea

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

55 conflicts on slot 0x6f641e3bc5…4312c3

← previous block·next block →recent activity