← previous blocknext block →recent activity

Analyzing

Block #76,087,995

23 transactions · 14 stateful · 2026-05-21 17:16:23 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #76,087,995  ·  23 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

0xc596390a…6c97

0xd32edf…ff58

9 touches
10 conflicts

0xdb95e18e…c73b

0x1b6862…e19c

4 touches
1 conflict

0x613f9dae…c021

0x34b655…2a6f

4 touches
1 conflict

0x9fc6ea79…e2dc

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf9b8ae99…32b4

0x34b655…2a6f

4 touches
1 conflict

0xfd784183…67bb

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

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 0xc596390a10…a46c97

← previous block·next block →recent activity