← previous blocknext block →recent activity

Analyzing

Block #97,568,321

33 transactions · 24 stateful · 2026-08-20 07:40:29 UTC

Parallelism

67/100

Blocked

63%

Avg conflicts / tx

1.85

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #97,568,321  ·  33 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

0x724324b1…6d89

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…0000

0x659bd0…a9da

6 touches
3 conflicts

0x7e28e55c…d05c

0x754704…b603

6 touches
3 conflicts

0x00000000…0002

0x659bd0…a9da

6 touches
3 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c1

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

55 conflicts on slot 0x724324b18d…1b6d89

← previous block·next block →recent activity