← previous blocknext block →recent activity

Analyzing

Block #98,678,079

19 transactions · 18 stateful · 2026-08-24 05:43:24 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,678,079  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x3c207e5c…7675

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0xbb3f3c…e046

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x70e677f5…e3bd

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x2f74f175…9284

0x2b46c0…1669

2 touches
0 conflicts

0x2f74f175…9285

0x2b46c0…1669

2 touches
0 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

6 conflicts on slot 0x3c207e5ce6…e47675

← previous block·next block →recent activity