← previous blocknext block →recent activity

Analyzing

Block #90,310,884

17 transactions · 15 stateful · 2026-07-25 21:37:38 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.82

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,310,884  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x60363fdd…9599

0xd32edf…ff58

7 touches
6 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0x0de8f3e9…a865

0x34b655…2a6f

6 touches
3 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x3e04662b…0da2

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0f2d78b1…7363

0x34b655…2a6f

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

6 conflicts on slot 0x60363fddc9…7f9599

← previous block·next block →recent activity