← previous blocknext block →recent activity

Analyzing

Block #77,517,389

29 transactions · 21 stateful · 2026-05-28 07:58:04 UTC

Parallelism

76/100

Blocked

43%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #77,517,389  ·  29 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x1f76de35…c119

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xce827910…ff22

0x065c9d…c394

8 touches
6 conflicts

0x7d42dc8b…fdb6

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x7ed092e4…041a

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

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 0x1f76de351d…eec119

← previous block·next block →recent activity