← previous blocknext block →recent activity

Analyzing

Block #77,350,617

35 transactions · 23 stateful · 2026-05-27 13:27:08 UTC

Parallelism

69/100

Blocked

61%

Avg conflicts / tx

1.71

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #77,350,617  ·  35 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x7e59a48d…1bd3

0xd32edf…ff58

21 touches
55 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x65903ef9…2567

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0xd1480c90…ae09

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

55 conflicts on slot 0x7e59a48dba…f71bd3

← previous block·next block →recent activity