← previous blocknext block →recent activity

Analyzing

Block #79,406,691

22 transactions · 18 stateful · 2026-06-06 02:01:06 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #79,406,691  ·  22 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

0x82ef65fa…d57e

0xd32edf…ff58

13 touches
21 conflicts

0x527f20e3…82e7

0x754704…b603

6 touches
3 conflicts

0xd9f1e40f…09a3

0x3bd359…433a

6 touches
3 conflicts

0x78694995…f66e

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

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

21 conflicts on slot 0x82ef65fa6b…a8d57e

← previous block·next block →recent activity