← previous blocknext block →recent activity

Analyzing

Block #75,516,902

30 transactions · 21 stateful · 2026-05-19 01:48:18 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,516,902  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x52d4b7f0…52d5

0xd32edf…ff58

11 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xc009105d…96f7

0x8d66a4…3095

4 touches
1 conflict

0x50e10826…843b

0x8d66a4…3095

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

15 conflicts on slot 0x52d4b7f070…ba52d5

← previous block·next block →recent activity