← previous blocknext block →recent activity

Analyzing

Block #90,957,271

21 transactions · 17 stateful · 2026-07-28 04:02:03 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,957,271  ·  21 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

0x51f9d3fe…0c28

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0x4054d247…5ddb

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0x580c6fe7…0fe8

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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 0x51f9d3fe28…b70c28

← previous block·next block →recent activity