← previous blocknext block →recent activity

Analyzing

Block #86,057,473

27 transactions · 21 stateful · 2026-07-06 21:28:26 UTC

Parallelism

74/100

Blocked

48%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,057,473  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd5ebd193…e7d1

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x17a7f697…dcb5

0x1b6862…e19c

4 touches
1 conflict

0x18cf3003…51d1

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

21 conflicts on slot 0xd5ebd1939a…4be7d1

← previous block·next block →recent activity