← previous blocknext block →recent activity

Analyzing

Block #73,687,188

29 transactions · 19 stateful · 2026-05-10 14:02:03 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.93

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,687,188  ·  29 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

0xc43373fd…9018

0xd32edf…ff58

13 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xa60a7778…9ff7

0x065c9d…c394

4 touches
1 conflict

0x93afca4c…b47c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

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

21 conflicts on slot 0xc43373fdc3…739018

← previous block·next block →recent activity