← previous blocknext block →recent activity

Analyzing

Block #87,710,021

22 transactions · 19 stateful · 2026-07-14 13:36:10 UTC

Parallelism

82/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,710,021  ·  22 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

0xa55236bc…c718

0xd32edf…ff58

7 touches
6 conflicts

0x4f1e16d4…4833

0x34b655…2a6f

4 touches
1 conflict

0x94ba9c4a…41d8

0x34b655…2a6f

4 touches
1 conflict

0xba7adbe7…f88a

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xf0d3064f…ccd2

0x34b655…2a6f

4 touches
1 conflict

0xf31b6b3f…055e

0x34b655…2a6f

4 touches
1 conflict

0x8a705be8…7ac4

0xc8689a…ee79

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 0xa55236bc8f…4fc718

← previous block·next block →recent activity