← previous blocknext block →recent activity

Analyzing

Block #83,632,783

23 transactions · 19 stateful · 2026-06-25 16:04:57 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,632,783  ·  23 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

0xb001a3fe…5348

0xd32edf…ff58

11 touches
15 conflicts

0xff96dc9b…93d7

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0x784d7a94…949e

0x1b6862…e19c

8 touches
6 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

15 conflicts on slot 0xb001a3fe87…615348

← previous block·next block →recent activity