← previous blocknext block →recent activity

Analyzing

Block #75,790,010

31 transactions · 21 stateful · 2026-05-20 08:09:45 UTC

Parallelism

68/100

Blocked

71%

Avg conflicts / tx

1.81

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,790,010  ·  31 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x1262316b…66c4

0xd32edf…ff58

19 touches
45 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 conflicts

0x0f94ee4c…189d

0x1b6862…e19c

8 touches
6 conflicts

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

45 conflicts on slot 0x1262316bbb…af66c4

← previous block·next block →recent activity