← previous blocknext block →recent activity

Analyzing

Block #96,694,120

27 transactions · 22 stateful · 2026-08-17 05:36:14 UTC

Parallelism

70/100

Blocked

59%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #96,694,120  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xb5456591…96a1

0xd32edf…ff58

13 touches
21 conflicts

0xe9452241…95a3

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x03aa8b26…118a

0x34b655…2a6f

6 touches
3 conflicts

0x990332f1…aae7

0x34b655…2a6f

6 touches
3 conflicts

0xb0e4f69d…34e1

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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

21 conflicts on slot 0xb5456591cd…9996a1

← previous block·next block →recent activity