← previous blocknext block →recent activity

Analyzing

Block #74,417,334

25 transactions · 19 stateful · 2026-05-13 23:14:03 UTC

Parallelism

80/100

Blocked

42%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,417,334  ·  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

0x90422366…70c4

0xd32edf…ff58

7 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x6191b0bd…6a6d

0x065c9d…c394

4 touches
1 conflict

0xaa2e7a15…3f12

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

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 0x9042236657…4470c4

← previous block·next block →recent activity