← previous blocknext block →recent activity

Analyzing

Block #74,671,597

23 transactions · 15 stateful · 2026-05-15 03:34:54 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,671,597  ·  23 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

0x58e2511f…492d

0xd32edf…ff58

9 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x5a7fe7ea…c5b6

0x0555e3…2b9c

2 touches
0 conflicts

0x644ba748…ce1a

0x0555e3…2b9c

2 touches
0 conflicts

0x8e80434a…a96d

0x0555e3…2b9c

2 touches
0 conflicts

0x19655ba9…b374

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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

10 conflicts on slot 0x58e2511fe9…03492d

← previous block·next block →recent activity