← previous blocknext block →recent activity

Analyzing

Block #87,418,701

32 transactions · 21 stateful · 2026-07-13 05:07:16 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,418,701  ·  32 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

0xc160d871…d719

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1358e07c…119c

0x065c9d…c394

4 touches
1 conflict

0x160f117d…8e90

0x065c9d…c394

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x83058c4e…c7cc

0x34b655…2a6f

4 touches
1 conflict

0xda46a376…f6a6

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

3 conflicts on slot 0xc160d871a7…03d719

← previous block·next block →recent activity