← previous blocknext block →recent activity

Analyzing

Block #73,673,761

32 transactions · 24 stateful · 2026-05-10 12:31:26 UTC

Parallelism

59/100

Blocked

63%

Avg conflicts / tx

1.81

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,673,761  ·  32 txs across 13 waves  ·  depth 13
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

wave w12

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

0xe0f39e32…bcfe

0xd32edf…ff58

17 touches
36 conflicts

0xc9e97522…3519

0x2a68ba…90c5

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x0ac31945…2c72

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x14af78bb…aeda

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x5d8872a6…1e35

0x065c9d…c394

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

36 conflicts on slot 0xe0f39e3277…e5bcfe

← previous block·next block →recent activity