← previous blocknext block →recent activity

Analyzing

Block #75,501,967

20 transactions · 16 stateful · 2026-05-19 00:06:00 UTC

Parallelism

70/100

Blocked

31%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,501,967  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7f8a75ce…ea7d

0xd32edf…ff58

11 touches
15 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x489cb750…7069

0x065c9d…c394

2 touches
0 conflicts

0x905eb956…1d6e

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0018

0x1b6862…e19c

2 touches
0 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

15 conflicts on slot 0x7f8a75ce3f…91ea7d

← previous block·next block →recent activity