← previous blocknext block →recent activity

Analyzing

Block #85,756,556

23 transactions · 17 stateful · 2026-07-05 12:01:59 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,756,556  ·  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

0xa458570e…c8ea

0xd32edf…ff58

11 touches
15 conflicts

0x6aa624fd…a851

0x1b6862…e19c

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe7dc8cbb…fb6c

0x34b655…2a6f

4 touches
1 conflict

0xfa1a8731…ca65

0x34b655…2a6f

4 touches
1 conflict

0xffb8950c…23c6

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

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

15 conflicts on slot 0xa458570e6b…c5c8ea

← previous block·next block →recent activity