← previous blocknext block →recent activity

Analyzing

Block #75,095,733

27 transactions · 19 stateful · 2026-05-17 02:47:15 UTC

Parallelism

56/100

Blocked

63%

Avg conflicts / tx

2.48

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #75,095,733  ·  27 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x6c684273…f5fd

0xd32edf…ff58

23 touches
66 conflicts

0x18aed20c…48f3

0x000000…012a

4 touches
1 conflict

0x7c403af1…31b1

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0002

0xd5b70d…615b

4 touches
1 conflict

0x00000000…0004

0xd5b70d…615b

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

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

66 conflicts on slot 0x6c68427320…f6f5fd

← previous block·next block →recent activity