← previous blocknext block →recent activity

Analyzing

Block #98,474,543

17 transactions · 15 stateful · 2026-08-23 12:06:50 UTC

Parallelism

65/100

Blocked

60%

Avg conflicts / tx

1.12

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,474,543  ·  17 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

0x1f37f77c…f6db

0xd32edf…ff58

11 touches
15 conflicts

0x30908823…a62d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x0b0611f7…e63a

0x34b655…2a6f

4 touches
1 conflict

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0x00add2aa…d923

0x065c9d…c394

3 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 0x1f37f77c70…ecf6db

← previous block·next block →recent activity