← previous blocknext block →recent activity

Analyzing

Block #75,943,713

27 transactions · 17 stateful · 2026-05-21 01:15:01 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,943,713  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa22b3a8a…c27d

0xd32edf…ff58

5 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x97e4c862…4419

0x34b655…2a6f

4 touches
1 conflict

0xb3aa2022…9e09

0x34b655…2a6f

4 touches
1 conflict

0xd0fbf889…ac50

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

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

3 conflicts on slot 0xa22b3a8af9…29c27d

← previous block·next block →recent activity