← previous blocknext block →recent activity

Analyzing

Block #86,818,378

23 transactions · 20 stateful · 2026-07-10 10:13:30 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,818,378  ·  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

0xd45c5a71…ad64

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x36890fff…f3d1

0x34b655…2a6f

4 touches
1 conflict

0x55d5cc2c…4efa

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x8d888c90…5479

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 0xd45c5a7115…5fad64

← previous block·next block →recent activity