← previous blocknext block →recent activity

Analyzing

Block #96,610,995

24 transactions · 23 stateful · 2026-08-16 22:38:10 UTC

Parallelism

71/100

Blocked

52%

Avg conflicts / tx

1.58

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,610,995  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x991b7c68…0687

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…00c9

0x34b655…2a6f

8 touches
6 conflicts

0xfb4cb196…8c4a

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x4964acbd…62f4

0x34b655…2a6f

6 touches
3 conflicts

0x9b2d3bee…8eeb

0x34b655…2a6f

6 touches
3 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

21 conflicts on slot 0x991b7c6880…a90687

← previous block·next block →recent activity