← previous blocknext block →recent activity

Analyzing

Block #75,845,831

25 transactions · 15 stateful · 2026-05-20 14:22:44 UTC

Parallelism

80/100

Blocked

60%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,845,831  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbf660235…ff61

0xd32edf…ff58

9 touches
10 conflicts

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xdbadf6b0…43b2

0x33176b…e078

4 touches
1 conflict

0xa1087a5c…66c4

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 0xbf660235ab…d5ff61

← previous block·next block →recent activity