← previous blocknext block →recent activity

Analyzing

Block #96,603,482

37 transactions · 33 stateful · 2026-08-16 22:00:23 UTC

Parallelism

73/100

Blocked

67%

Avg conflicts / tx

2.19

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #96,603,482  ·  37 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xeb928396…033f

0xd32edf…ff58

19 touches
45 conflicts

0x033cf007…136d

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xb9834665…e363

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0xac79a0c7…be15

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

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

45 conflicts on slot 0xeb928396ac…b5033f

← previous block·next block →recent activity