← previous blocknext block →recent activity

Analyzing

Block #86,137,573

47 transactions · 35 stateful · 2026-07-07 06:22:56 UTC

Parallelism

77/100

Blocked

69%

Avg conflicts / tx

1.57

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #86,137,573  ·  47 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x0883533f…b437

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0002

0x04fdea…47d7

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xc1ceff4b…04a0

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

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

36 conflicts on slot 0x0883533f3a…88b437

← previous block·next block →recent activity