← previous blocknext block →recent activity

Analyzing

Block #98,552,328

22 transactions · 18 stateful · 2026-08-23 18:48:04 UTC

Parallelism

41/100

Blocked

72%

Avg conflicts / tx

1.86

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #98,552,328  ·  22 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x5c0cc9e8…b2f8

0xd32edf…ff58

11 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002d

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xdbc6e634…e16a

0x1b6862…e19c

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

15 conflicts on slot 0x5c0cc9e872…50b2f8

← previous block·next block →recent activity