← previous blocknext block →recent activity

Analyzing

Block #95,023,908

32 transactions · 27 stateful · 2026-08-11 09:19:15 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,023,908  ·  32 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

0x78f09116…5ce5

0xd32edf…ff58

11 touches
15 conflicts

0x3ed31132…62b6

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x3bd55803…5d4f

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

15 conflicts on slot 0x78f0911683…6b5ce5

← previous block·next block →recent activity