← previous blocknext block →recent activity

Analyzing

Block #83,862,421

22 transactions · 19 stateful · 2026-06-26 17:37:10 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,862,421  ·  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

0xe897306c…9718

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0018

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0xff96dc9b…93d7

0x065c9d…c394

4 touches
1 conflict

0x0b16149e…7d4d

0x065c9d…c394

4 touches
1 conflict

0x785889c9…0603

0x34b655…2a6f

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 0xe897306ca3…fb9718

← previous block·next block →recent activity