← previous blocknext block →recent activity

Analyzing

Block #86,705,822

23 transactions · 20 stateful · 2026-07-09 21:41:36 UTC

Parallelism

74/100

Blocked

35%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,705,822  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x9824455e…d1c3

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0xd5b10148…e632

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x1e01ff67…ec41

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

15 conflicts on slot 0x9824455e20…b4d1c3

← previous block·next block →recent activity