← previous blocknext block →recent activity

Analyzing

Block #82,023,974

25 transactions · 22 stateful · 2026-06-18 04:59:50 UTC

Parallelism

64/100

Blocked

59%

Avg conflicts / tx

1.12

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #82,023,974  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x6b01691d…4f11

0xd32edf…ff58

9 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x76d1e78d…7877

0x40c49f…2af0

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb4

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

10 conflicts on slot 0x6b01691d3f…f94f11

← previous block·next block →recent activity