← previous blocknext block →recent activity

Analyzing

Block #98,456,528

21 transactions · 19 stateful · 2026-08-23 10:36:00 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,456,528  ·  21 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

0x3ff9588b…650d

0xd32edf…ff58

11 touches
15 conflicts

0x8f84702c…c5f9

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c3

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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

15 conflicts on slot 0x3ff9588b3e…37650d

← previous block·next block →recent activity