← previous blocknext block →recent activity

Analyzing

Block #79,407,609

32 transactions · 23 stateful · 2026-06-06 02:07:12 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.66

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #79,407,609  ·  32 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xed27b4fb…5147

0xd32edf…ff58

11 touches
15 conflicts

0xab2a87f1…eb02

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x299a5a83…5416

0x065c9d…c394

5 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

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

15 conflicts on slot 0xed27b4fb71…c65147

← previous block·next block →recent activity