← previous blocknext block →recent activity

Analyzing

Block #93,363,981

34 transactions · 29 stateful · 2026-08-05 13:53:45 UTC

Parallelism

68/100

Blocked

62%

Avg conflicts / tx

2.26

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #93,363,981  ·  34 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

0x5cf20278…8d25

0xd32edf…ff58

21 touches
55 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xfecb18c0…01ed

0x34b655…2a6f

10 touches
10 conflicts

0xfed09e59…a493

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0x9fa1409b…0e59

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

55 conflicts on slot 0x5cf202782b…cb8d25

← previous block·next block →recent activity