← previous blocknext block →recent activity

Analyzing

Block #73,672,963

25 transactions · 19 stateful · 2026-05-10 12:26:02 UTC

Parallelism

80/100

Blocked

32%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,672,963  ·  25 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

0x5b3d5fb5…c71a

0xd32edf…ff58

7 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x4d1acd7c…f345

0x5e1b1a…7777

4 touches
1 conflict

0x00000000…0000

0x75c3ab…4f0d

4 touches
1 conflict

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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

6 conflicts on slot 0x5b3d5fb55f…5ac71a

← previous block·next block →recent activity