← previous blocknext block →recent activity

Analyzing

Block #86,619,646

25 transactions · 21 stateful · 2026-07-09 12:04:59 UTC

Parallelism

88/100

Blocked

24%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,619,646  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf0774813…195f

0xd32edf…ff58

5 touches
3 conflicts

0xbf6e10ed…7fad

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x94ba9c4a…41d8

0x34b655…2a6f

4 touches
1 conflict

0x27b5413c…c0e7

0x5afd3e…7620

2 touches
0 conflicts

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

3 conflicts on slot 0xf07748130f…eb195f

← previous block·next block →recent activity