← previous blocknext block →recent activity

Analyzing

Block #98,642,888

36 transactions · 34 stateful · 2026-08-24 02:39:56 UTC

Parallelism

69/100

Blocked

59%

Avg conflicts / tx

1.97

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #98,642,888  ·  36 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x2d6e69fd…d3a5

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0xa6afd3…d132

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x6fd9ae7c…e984

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 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

36 conflicts on slot 0x2d6e69fde8…46d3a5

← previous block·next block →recent activity