← previous blocknext block →recent activity

Analyzing

Block #93,677,250

26 transactions · 21 stateful · 2026-08-06 16:08:38 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.54

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,677,250  ·  26 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

0x97f79c87…0165

0xd32edf…ff58

7 touches
6 conflicts

0x9ba6ae4a…90cb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x69017fce…85bf

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…00c9

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

6 conflicts on slot 0x97f79c8756…ea0165

← previous block·next block →recent activity