← previous blocknext block →recent activity

Analyzing

Block #86,620,921

23 transactions · 20 stateful · 2026-07-09 12:13:28 UTC

Parallelism

78/100

Blocked

45%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,620,921  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x9e9303b0…80ef

0xd32edf…ff58

9 touches
10 conflicts

0xa29182a1…c12c

0x34b655…2a6f

6 touches
3 conflicts

0x7f6581c2…7ade

0x34b655…2a6f

4 touches
1 conflict

0x82fbdeba…e163

0x34b655…2a6f

4 touches
1 conflict

0x8eb0ac6b…a73a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfd3ea588…319c

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

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

10 conflicts on slot 0x9e9303b025…a480ef

← previous block·next block →recent activity