← previous blocknext block →recent activity

Analyzing

Block #90,232,777

17 transactions · 15 stateful · 2026-07-25 15:02:24 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.76

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,232,777  ·  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

0x56e2d311…12d7

0xd32edf…ff58

7 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x6aa624fd…a852

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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 0x56e2d311d6…a412d7

← previous block·next block →recent activity