← previous blocknext block →recent activity

Analyzing

Block #73,964,219

21 transactions · 21 stateful · 2026-05-11 20:57:03 UTC

Parallelism

67/100

Blocked

48%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,964,219  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf4b5b0c0…423c

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

6 touches
3 conflicts

0xe75ce681…ba61

0x188d58…ea8e

6 touches
3 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

21 conflicts on slot 0xf4b5b0c064…83423c

← previous block·next block →recent activity