← previous blocknext block →recent activity

Analyzing

Block #97,558,937

25 transactions · 20 stateful · 2026-08-20 06:52:34 UTC

Parallelism

72/100

Blocked

45%

Avg conflicts / tx

0.68

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,558,937  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd4f3c781…f5ca

0xd32edf…ff58

9 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x3e04662b…0da3

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x4f58b18a…ecc1

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

10 conflicts on slot 0xd4f3c781e1…b0f5ca

← previous block·next block →recent activity