← previous blocknext block →recent activity

Analyzing

Block #90,384,782

18 transactions · 17 stateful · 2026-07-26 03:55:36 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,384,782  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x3645c1e7…e6ce

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa7d3e24a…0eb8

0x34b655…2a6f

6 touches
3 conflicts

0x3f33f55b…32cb

0x34b655…2a6f

4 touches
1 conflict

0x3f85f288…7c97

0x34b655…2a6f

4 touches
1 conflict

0x41e2ea73…ddf8

0x34b655…2a6f

4 touches
1 conflict

0x48017206…f344

0x34b655…2a6f

4 touches
1 conflict

0x6fbc2e5a…e69c

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

10 conflicts on slot 0x3645c1e704…e7e6ce

← previous block·next block →recent activity