← previous blocknext block →recent activity

Analyzing

Block #87,133,543

21 transactions · 19 stateful · 2026-07-11 21:19:39 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,133,543  ·  21 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

0xed2e12ef…e082

0xd32edf…ff58

7 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xd5ab2f5b…092b

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x7d063859…5753

0x34b655…2a6f

4 touches
1 conflict

0x389d5ec7…0367

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4a2

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

6 conflicts on slot 0xed2e12efaa…42e082

← previous block·next block →recent activity