← previous blocknext block →recent activity

Analyzing

Block #74,259,861

23 transactions · 20 stateful · 2026-05-13 05:46:19 UTC

Parallelism

48/100

Blocked

65%

Avg conflicts / tx

2.22

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,259,861  ·  23 txs across 12 waves  ·  depth 12
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

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

0xb4f0072b…e868

0xd32edf…ff58

17 touches
36 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x659bda06…1397

0x065c9d…c394

7 touches
6 conflicts

0x7e28e55c…d05c

0x754704…b603

6 touches
3 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x659bd0…a9da

6 touches
3 conflicts

0x00000000…0001

0x659bd0…a9da

6 touches
3 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 0xb4f0072b2b…75e868

← previous block·next block →recent activity